Repository navigation
fix(flux-operator): flux-operator 0.61.0, sthings-cluster 0.3.20, repo condition on instance - #167
Merged
Merged
Conversation
…o condition on instance - flux-operator chart 0.28.0 -> 0.61.0 (latest, 2026-10-01). The default was 33 minors behind; blueprints/flux bootstrap overrides it with its own --operator-version default (0.47.0), so callers that rely on this file's default got 0.28.0. - sthings-cluster 0.3.15 -> 0.3.20 for the secrets and FluxInstance releases. helmfile template with the same state values renders the Secrets and the FluxInstance byte-identical on both versions. - The stuttgart-things repository was gated on hasKey "instances" while the release uses .Values.instance: an instance without secrets failed with 'repo stuttgart-things not found' (reproduced on main; passes now). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
cicd/flux-operator.yaml.gotmpl, which the Flux bootstrap in blueprints/flux uses (--helmfile-ref git::https://github.com/stuttgart-things/helm.git@cicd/flux-operator.yaml.gotmpl):hasKey .Values "instances"hasKey .Values "instance"Renovate has the annotation but never opened a PR for the operator version.
Bug
The release uses
.Values.instance, but the repository block checkedinstances. It only worked whensecretswas also set. An instance-only render onmainfails:With this change it renders.
Checked
helmfile templatewith the same state values (two secrets + a SOPS-enabled instance), comparing the old and new pins:Secret/git-token-auth,Secret/sops-ageandFluxInstance/fluxare identical. Only the flux-operator chart itself differs.Note
blueprints/flux
bootstrappassesversion=<operatorVersion>(default0.47.0in v3.2.2), which overrides this default. Pass--operator-version 0.61.0until the blueprints default moves too.🤖 Generated with Claude Code