Skip to content

fix(chart): drop the default image pull secret - #211

Merged
dmf-cms-automerge[bot] merged 1 commit into
mainfrom
fix/852-no-default-pull-secret
Nov 7, 2026
Merged

dmf-cms-automerge[bot] merged 1 commit into
mainfrom
fix/852-no-default-pull-secret

Conversation

@znerol2

@znerol2 znerol2 commented Nov 7, 2026

Copy link
Copy Markdown
Contributor

Summary

The chart defaulted imagePullSecrets to registry-creds, a secret that no role, script or playbook creates. Every console pod logged FailedToRetrieveImagePullSecret. Pulls worked only because the platform registry serves anonymous reads (ADR-0033), so the warning was noise. If reads ever needed a login, that noise would also hide the real failure.

The default is now imagePullSecrets: [], with a comment saying to set it only when the registry needs credentials for reads.

Verification

  • CI-style helm template:
    • With CI's --set values, there is no imagePullSecrets by default.
    • --set imagePullSecrets[0].name=x renders the override.
    • main renders registry-creds.
  • helm lint and the version sync check pass.
  • Nothing depends on the old default. There are no references in this repo, in dmf-infra or in dmf-env. The cms role's values template never sets the field.
  • Live on a sandbox: playbook 650 with this chart rolled the console. The new pod has no imagePullSecrets, is ready, and pulled from the platform registry, with no FailedToRetrieveImagePullSecret event.

Review

One round of adversarial review. It passed.

Closes dmfdeploy/dmfdeploy#852

The chart named a registry-creds pull secret that nothing creates, so
every console pod logged FailedToRetrieveImagePullSecret. Pulls only
worked because the platform registry serves anonymous reads, and the
warning would have hidden a real failure if that changed.

Default imagePullSecrets to an empty list and say when to set it.

Closes dmfdeploy/dmfdeploy#852

Signed-off-by: znerol2 <6800371+znerol2@users.noreply.github.com>
@znerol2
znerol2 requested a review from a team as a code owner November 7, 2026 13:45
@dmf-cms-automerge
dmf-cms-automerge Bot enabled auto-merge (rebase) November 7, 2026 13:49

@lkirc lkirc left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Static review of 0760ef3: no blocking findings.

The empty-list default cleanly omits imagePullSecrets while preserving the documented opt-in override. Required checks and approval gates pass.

@dmf-cms-automerge
dmf-cms-automerge Bot merged commit 3b8547c into main Nov 7, 2026
18 checks passed
@dmf-cms-automerge
dmf-cms-automerge Bot deleted the fix/852-no-default-pull-secret branch November 7, 2026 13:57
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.

dmf-cms chart names an image pull secret that nothing creates

2 participants