Skip to content

fix: Remove the hardcoded image repository from values.yaml - #445

Open
lfrancke wants to merge 1 commit into
mainfrom
push-zllousrqvstx
Open

fix: Remove the hardcoded image repository from values.yaml#445
lfrancke wants to merge 1 commit into
mainfrom
push-zllousrqvstx

Conversation

@lfrancke

@lfrancke lfrancke commented Aug 7, 2026

Copy link
Copy Markdown
Member

Description

I'm looking into adding a Values schema and had Claude analyse our values file. commons-operator is the only one setting image.repository in its own values file. The others leave it to the registry overlay in deploy/helm/commons-operator/values/.

In addition the value was also wrong. So, due to the overlay this is not actively broken but its still better to be consistent I think.

No behaviour change for published charts as the overlay wins anyway.

Definition of Done Checklist

  • Not all of these items are applicable to all PRs, the author should update this template to only leave the boxes in that are relevant
  • Please make sure all these things are done and tick the boxes

Author

  • Changes are OpenShift compatible
  • CRD changes approved
  • CRD documentation for all fields, following the style guide.
  • Helm chart can be installed and deployed operator works
  • Integration tests passed (for non trivial changes)
  • Changes need to be "offline" compatible
  • Links to generated (nightly) docs added
  • Release note snippet added

Reviewer

  • Code contains useful comments
  • Code contains useful logging statements
  • (Integration-)Test cases added
  • Documentation added or updated. Follows the style guide.
  • Changelog updated
  • Cargo.toml only contains references to git tags (not specific commits or branches)

Acceptance

  • Feature Tracker has been updated
  • Proper release label has been added
  • Links to generated (nightly) docs added
  • Release note snippet added
  • Add type/deprecation label & add to the deprecation schedule
  • Add type/experimental label & add to the experimental features tracker

commons-operator was the only operator setting image.repository in its own
values.yaml. The other 13 non-CSI operators leave it to the registry overlay in
deploy/helm/commons-operator/values/, which publish-helm-chart merges on top at
package time.

The value was also wrong in shape. operator.image renders
"{repository}/{Chart.Name}:{tag}", so repository is the namespace and the chart
name is appended. The hardcoded value already contained the name, so had it ever
taken effect it would have produced .../sdp/commons-operator/commons-operator.

No behaviour change for published charts: the overlay wins the merge either way.
@lfrancke
lfrancke marked this pull request as ready for review August 7, 2026 08:20
@lfrancke lfrancke self-assigned this Aug 7, 2026
@lfrancke lfrancke moved this to Development: Waiting for Review in Stackable Engineering Aug 7, 2026
@sbernauer
sbernauer requested a review from Techassi August 7, 2026 08:21
@Techassi Techassi moved this from Development: Waiting for Review to Development: In Review in Stackable Engineering Aug 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Development: In Review

Development

Successfully merging this pull request may close these issues.

2 participants