Flux v2.8.6 released on 21-04-2026
Flux v2.8.6 is out now. Operators running helm-controller, kustomize-controller, source-controller, image-automation-controller or notification-controller get a set of bug fixes and small improvements that tidy up Helm post-rendering, Git performance and notification handling.
Follow the Upgrade Procedure for Flux v2.7+ on GitHub when moving from v2.6, and see the full changelog on the Flux repository for release details: Upgrade Procedure for Flux v2.7+ and Full Changelog.
What’s in this release
- helm-controller: fixes a post-renderer conflict between overlapping hooks and templates, and ignores “force replace” when server-side apply is enabled; component bumped to v1.5.4.
- notification-controller: restores forwarding of commit status events for generic providers and tightens GCR Receiver verification by requiring an
audiencefield on the Receiver secret; component updated to v1.8.4. - kustomize-controller, source-controller and image-automation-controller: adds the
MigrateAPIVersionfeature gate for managed-field API migrations and updates go-git to v5.18.0 for improved Git operation performance; component versions updated (kustomize v1.8.4, source v1.8.3, image-automation v1.1.2).
Upgrade notes
- The GCR Receiver now requires an
audiencefield on the Receiver secret; add that field before upgrading where relevant. This field will become mandatory in Flux v2.9. - For a smooth upgrade from v2.6 follow the published Upgrade Procedure for Flux v2.7+ and consult the full changelog and component changelogs linked from the release for any component-specific notes.
Tell the project about your upgrade experience or any issues you hit via the Flux GitHub discussion and issue tracker so maintainers and other users can follow up.
