Skip to content

Add imagePullSecrets and extend imagePullPolicy to all chart images#372

Open
Bhawanishanker22 wants to merge 46 commits into
debezium:mainfrom
Bhawanishanker22:fix-imagepullsecrets-1851
Open

Add imagePullSecrets and extend imagePullPolicy to all chart images#372
Bhawanishanker22 wants to merge 46 commits into
debezium:mainfrom
Bhawanishanker22:fix-imagepullsecrets-1851

Conversation

@Bhawanishanker22
Copy link
Copy Markdown

@Bhawanishanker22 Bhawanishanker22 commented Apr 24, 2026

Fixes debezium/debezium#1851

Description

Extends imagePullPolicy support and adds imagePullSecrets configuration
for all container images in the Helm chart.

Changes

values.yaml

  • Added top-level imagePullSecrets: [] — global pull secrets applied to all images by default
  • Added stage.imagePullSecrets — per-component override for the stage image
  • Added conductor.imagePullSecrets — per-component override for the conductor image
  • Added conductor.descriptors.official.imagePullPolicy — previously missing pull policy for the descriptors OCI image
  • Added conductor.descriptors.official.imagePullSecrets — per-component override for the descriptors image
  • Added server.imagePullPolicy — previously missing pull policy for Debezium Server instances
  • Added server.imagePullSecrets — per-component override for the Debezium Server image

conductor-deployment.yaml

  • Injected imagePullSecrets block into pod spec using a global → per-component fallback pattern

stage-deployment.yaml

  • Injected imagePullSecrets block into pod spec using the same global → per-component fallback pattern

README.md

  • Added documentation rows for all 8 new configuration fields

Behaviour

  • Per-component imagePullSecrets overrides (does not merge with) the global list — consistent with standard Kubernetes and Helm chart conventions
  • All new fields are optional and default to empty — fully backward compatible with existing installations
  • When both global and component secrets are empty, no imagePullSecrets key is rendered in the pod spec

PR Checklist

  • I have read the contribution guidelines and the governance document on PR expectations.
  • Minimal changes to code not directly related to your change (e.g. no unnecessary formatting changes or refactoring to existing code)
  • One feature/change per PR unless tightly coupled
  • Do a rebase on upstream main

jcechace added 30 commits April 24, 2024 15:35
@Bhawanishanker22 Bhawanishanker22 force-pushed the fix-imagepullsecrets-1851 branch from 041a921 to 2dda383 Compare April 24, 2026 07:13
Comment thread helm/templates/conductor-deployment.yaml
Comment thread helm/values.yaml Outdated
Comment thread helm/values.yaml
@mfvitale
Copy link
Copy Markdown
Member

@Bhawanishanker22 thanks for the PR. I left some comments.

@github-actions
Copy link
Copy Markdown

Hi @Bhawanishanker22, thanks for your contribution. Please prefix the commit message(s) with the debezium/dbz#xxx GitHub issue key.

@Bhawanishanker22 Bhawanishanker22 force-pushed the fix-imagepullsecrets-1851 branch from 9e5c5d4 to a07a2f7 Compare April 29, 2026 18:17
@github-actions
Copy link
Copy Markdown

Hi @Bhawanishanker22, thanks for your contribution. Please prefix the commit message(s) with the debezium/dbz#xxx GitHub issue key.

…Secrets, add ORAS credentials via secretKeyRef, remove unsupported imagePullPolicy from server

Signed-off-by: Bhawani Shanker Sharma <bhawanishanker2005@gmail.com>
@Bhawanishanker22 Bhawanishanker22 force-pushed the fix-imagepullsecrets-1851 branch from a07a2f7 to e336c99 Compare April 29, 2026 18:17
@Bhawanishanker22
Copy link
Copy Markdown
Author

@mfvitale The 2 failing tests in Run tests (ConnectionValidatorFactoryTest.shouldReturnDatabaseValidatorForOracle and PulsarConnectionValidatorTest.shouldFailValidationWithEmptyServiceHttpUrl) are failing with "Failed to start quarkus" — a Quarkus startup error in the CI environment unrelated to the changes in this PR. These tests depend on Oracle and Pulsar Testcontainers infrastructure. Could you confirm if these are pre-existing flaky tests in CI?

@mfvitale
Copy link
Copy Markdown
Member

@Bhawanishanker22 could you please rebase with the latest main changes. This should solve the unrelated test failures.

@github-actions
Copy link
Copy Markdown

❌ Developer Certificate of Origin (DCO) check failed.

Hi @Bhawanishanker22, please sign off all commits with:

git commit -s

If pull request commits are not signed off, the pull request cannot be merged. For more information about why this is required, please see our blog about contribution requirement changes.

@github-actions
Copy link
Copy Markdown

Hi @Bhawanishanker22, thanks for your contribution. Please prefix the commit message(s) with the debezium/dbz#xxx GitHub issue key.

…all chart images

Signed-off-by: Bhawani Shanker Sharma <bhawanishanker2005@gmail.com>
…all chart images

Signed-off-by: Bhawani Shanker Sharma <bhawanishanker2005@gmail.com>
@Bhawanishanker22 Bhawanishanker22 force-pushed the fix-imagepullsecrets-1851 branch from a3ce6e3 to 1c93f70 Compare May 15, 2026 05:53
@github-actions
Copy link
Copy Markdown

Hi @Bhawanishanker22, thanks for your contribution. Please prefix the commit message(s) with the debezium/dbz#xxx GitHub issue key.

@github-actions
Copy link
Copy Markdown

❌ Developer Certificate of Origin (DCO) check failed.

Hi @Bhawanishanker22, please sign off all commits with:

git commit -s

If pull request commits are not signed off, the pull request cannot be merged. For more information about why this is required, please see our blog about contribution requirement changes.

…all chart images

Signed-off-by: Bhawani Shanker Sharma <bhawanishanker2005@gmail.com>
@github-actions
Copy link
Copy Markdown

❌ Developer Certificate of Origin (DCO) check failed.

Hi @Bhawanishanker22, please sign off all commits with:

git commit -s

If pull request commits are not signed off, the pull request cannot be merged. For more information about why this is required, please see our blog about contribution requirement changes.

@github-actions
Copy link
Copy Markdown

Hi @Bhawanishanker22, thanks for your contribution. Please prefix the commit message(s) with the debezium/dbz#xxx GitHub issue key.

…all chart images

Signed-off-by: Bhawani Shanker Sharma <bhawanishanker2005@gmail.com>
@Bhawanishanker22 Bhawanishanker22 force-pushed the fix-imagepullsecrets-1851 branch from 5db9242 to e4805cb Compare May 15, 2026 05:59
@github-actions
Copy link
Copy Markdown

❌ Developer Certificate of Origin (DCO) check failed.

Hi @Bhawanishanker22, please sign off all commits with:

git commit -s

If pull request commits are not signed off, the pull request cannot be merged. For more information about why this is required, please see our blog about contribution requirement changes.

@github-actions
Copy link
Copy Markdown

Hi @Bhawanishanker22, thanks for your contribution. Please prefix the commit message(s) with the debezium/dbz#xxx GitHub issue key.

1 similar comment
@github-actions
Copy link
Copy Markdown

Hi @Bhawanishanker22, thanks for your contribution. Please prefix the commit message(s) with the debezium/dbz#xxx GitHub issue key.

@github-actions
Copy link
Copy Markdown

❌ Developer Certificate of Origin (DCO) check failed.

Hi @Bhawanishanker22, please sign off all commits with:

git commit -s

If pull request commits are not signed off, the pull request cannot be merged. For more information about why this is required, please see our blog about contribution requirement changes.

@Bhawanishanker22
Copy link
Copy Markdown
Author

@mfvitale Hi, I've added DCO sign-off to all commits via filter-branch and the commit messages already follow the debezium/dbz#1851 format. Could you please approve the workflows so the checks can re-run? Thanks!

@mfvitale
Copy link
Copy Markdown
Member

@Bhawanishanker22 I'm afraid that there is something bad with the commit history. Could you please do a clean rebase with the main? Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants