Add imagePullSecrets and extend imagePullPolicy to all chart images#372
Add imagePullSecrets and extend imagePullPolicy to all chart images#372Bhawanishanker22 wants to merge 46 commits into
Conversation
041a921 to
2dda383
Compare
|
@Bhawanishanker22 thanks for the PR. I left some comments. |
|
Hi @Bhawanishanker22, thanks for your contribution. Please prefix the commit message(s) with the debezium/dbz#xxx GitHub issue key. |
9e5c5d4 to
a07a2f7
Compare
|
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>
a07a2f7 to
e336c99
Compare
|
@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? |
|
@Bhawanishanker22 could you please rebase with the latest main changes. This should solve the unrelated test failures. |
|
❌ Developer Certificate of Origin (DCO) check failed. Hi @Bhawanishanker22, please sign off all commits with: 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. |
|
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>
a3ce6e3 to
1c93f70
Compare
|
Hi @Bhawanishanker22, thanks for your contribution. Please prefix the commit message(s) with the debezium/dbz#xxx GitHub issue key. |
|
❌ Developer Certificate of Origin (DCO) check failed. Hi @Bhawanishanker22, please sign off all commits with: 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>
|
❌ Developer Certificate of Origin (DCO) check failed. Hi @Bhawanishanker22, please sign off all commits with: 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. |
|
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>
5db9242 to
e4805cb
Compare
|
❌ Developer Certificate of Origin (DCO) check failed. Hi @Bhawanishanker22, please sign off all commits with: 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. |
|
Hi @Bhawanishanker22, thanks for your contribution. Please prefix the commit message(s) with the debezium/dbz#xxx GitHub issue key. |
1 similar comment
|
Hi @Bhawanishanker22, thanks for your contribution. Please prefix the commit message(s) with the debezium/dbz#xxx GitHub issue key. |
|
❌ Developer Certificate of Origin (DCO) check failed. Hi @Bhawanishanker22, please sign off all commits with: 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. |
|
@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! |
|
@Bhawanishanker22 I'm afraid that there is something bad with the commit history. Could you please do a clean rebase with the main? Thanks |
Fixes debezium/debezium#1851
Description
Extends
imagePullPolicysupport and addsimagePullSecretsconfigurationfor all container images in the Helm chart.
Changes
values.yamlimagePullSecrets: []— global pull secrets applied to all images by defaultstage.imagePullSecrets— per-component override for the stage imageconductor.imagePullSecrets— per-component override for the conductor imageconductor.descriptors.official.imagePullPolicy— previously missing pull policy for the descriptors OCI imageconductor.descriptors.official.imagePullSecrets— per-component override for the descriptors imageserver.imagePullPolicy— previously missing pull policy for Debezium Server instancesserver.imagePullSecrets— per-component override for the Debezium Server imageconductor-deployment.yamlimagePullSecretsblock into pod spec using a global → per-component fallback patternstage-deployment.yamlimagePullSecretsblock into pod spec using the same global → per-component fallback patternREADME.mdBehaviour
imagePullSecretsoverrides (does not merge with) the global list — consistent with standard Kubernetes and Helm chart conventionsimagePullSecretskey is rendered in the pod specPR Checklist
main