chore(muster): default versionRange 0.x -> 1.x (giantswarm#37164)#207
Merged
Conversation
The 0.x default froze every non-overriding installation on muster 0.24.0 since the 1.0.0 major bump (muster#968 removed JWT mode — dex is the sole SSO authority), so they never received the 1.x line, including the #37164 SSO re-exchange deauth fix (muster v1.0.7). The fleet already runs dex-only (shared-configs sets none of the removed keys: enableJWTMode/jwtSigningKey/localMint/M2M), and alligator already runs 1.0.7 healthy, so 1.x is safe everywhere. Crossing into 1.0.7+ re-authenticates every user once (mcp-oauth Valkey layout change, no legacy read-fallback). Only muster's versionRange changes; other components stay on 0.x. helm lint passes; render confirms muster OCIRepository semver = 1.x.
QuentinBisson
approved these changes
Jul 21, 2026
fiunchinho
reviewed
Jul 21, 2026
Comment on lines
+70
to
+74
| # 1.x: muster went 0.x -> 1.0.0 with #968 (JWT mode removed — muster no | ||
| # longer signs tokens, dex is the sole SSO authority). The fleet already | ||
| # runs dex-only (shared-configs sets no removed keys), so 1.x is safe | ||
| # everywhere. Crossing into 1.0.7+ re-authenticates every user once | ||
| # (mcp-oauth Valkey layout change, no legacy read-fallback). |
Member
There was a problem hiding this comment.
I don't think this comment adds value here. It's an explanation on why the PR is needed, but it's not useful as a code comment IMO.
Removed outdated comments regarding muster chart versioning.
fiunchinho
approved these changes
Jul 21, 2026
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
3 participants
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
Change the meta-package default
components.muster.versionRangefrom"0.x"to"1.x". Only muster's constraint changes; all other components stay on0.x.Why
muster crossed a major with muster#968 (
feat(oauth)!: remove JWT mode→v1.0.0): muster no longer signs tokens, dex is the sole SSO authority. The0.xdefault has since frozen every non-overriding installation on muster0.24.0, so they never received the1.xline — including the #37164 SSO re-exchange deauth fix (first released in musterv1.0.7).Safety — this is not a risky major jump
Audited the fleet for the surface
1.0.0removed (enableJWTMode/jwtSigningKey,localMint, M2MworkloadAudiences/actorDelegationPolicy):shared-configs(the fleet-wide base) sets none of them, and explicitly comments that muster v1.0.0 removed them.giantswarm-management-clusters,management-cluster-bases,adidas-/wepa-/bwi-management-clusters: zero usage.1.0.7healthy in prod (it uses>=0.0.0) — live proof the1.xline works fleet-wide.Rollout
Merge → chart release → each installation's base
OCIRepository(tracks agentic-platform>=0.1.0, 10m interval) re-resolves muster to the latest1.xand Flux upgrades it.Upgrade note: crossing into muster
1.0.7+re-authenticates every user exactly once — the mcp-oauth bump changes the Valkey token-storage layout with no legacy read-fallback; existing sessions do not carry over. One-time login, not a breakage (alligator already went through it).Verification
helm lintpasses.helm templateconfirms muster'sOCIRepository.spec.ref.semver = "1.x"; other components unchanged.Supersedes the per-MC override PR giantswarm-management-clusters#2239 (gazelle/glean), which will be closed in favor of this fleet-wide default.