You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Upgrade Flux and the audited Helm validation profile together #5851
Upgrade the deployed Flux distribution and its audited Helm validation profile together so required validation can use the matching current engine and toolchain.
Details
The maintainer approved including the matching platform upgrade in the CI repair. Audit Flux 2.10.0, helm-controller 1.7.1 and Helm 4.3.1 as one version-bound profile, including the actual published controller build metadata. Preserve source identity, approval, image-verification, render, rollout and recovery gates. Detailed scanner evidence stays in private local reports.
Checklist
Verify official distribution, controller image/build, SDK and compiler identities.
Update both declared cluster selectors and all consuming validation profiles consistently.
Prove actual rendering, post-rendering, selectors, cache invalidation and refusal behavior.
Re-run native dependency analysis on the resulting source and artifacts.
Pass current-head CI and permitted substantive review before protected merge.
Verify accepted main and deployed controller/health readback through the normal production path.
Dependencies
Part of #5843. Delivered through the existing consolidated candidate #5846; do not create a duplicate repair or waive parity checks.
Notes
A compiler-only bump is not the approved solution. If the current official controller cannot establish the required profile, retain that as a named blocker and prepare the smallest identity-bound repair with its native proof.
Post-merge check done (2026-11-11). Closing as completed.
Delivered by #5970 (merged 2026-11-10): the Helm controller and the matching validation renderer moved up together. The Flux base stayed on its recovery-compatible release.
Read-only production readback against main 33ba5b9:
helm-controller runs v1.7.1 at exactly the digest main pins (sha256:54526cc6ed12…). Both provider profiles declare that same override.
The FluxInstance is Ready on distribution 2.9.6, matching main.
All 49 HelmReleases are Ready. The live platform health check passes.
The objective is met: required validation now uses the same Helm engine as the production controller. Moving the whole Flux base to the current release, and dropping the one-off override, is a separate change with its own recovery proof. It is tracked in #6079.
Activity
devantler commentedon Nov 11, 2026
Post-merge check done (2026-11-11). Closing as completed.
Delivered by #5970 (merged 2026-11-10): the Helm controller and the matching validation renderer moved up together. The Flux base stayed on its recovery-compatible release.
Read-only production readback against main
33ba5b9:v1.7.1at exactly the digest main pins (sha256:54526cc6ed12…). Both provider profiles declare that same override.2.9.6, matching main.The objective is met: required validation now uses the same Helm engine as the production controller. Moving the whole Flux base to the current release, and dropping the one-off override, is a separate change with its own recovery proof. It is tracked in #6079.