Flux v2.8.6 released on 21-04-2026
Flux v2.8.6 is out now. Kubernetes operators and GitOps users get targeted bug fixes across multiple controllers and improved Git operation performance.
See the full changelog on GitHub: https://github.com/fluxcd/flux2/compare/v2.8.5…v2.8.6 and follow the Upgrade Procedure for Flux v2.7+ for a smooth migration from v2.6: https://github.com/fluxcd/flux2/discussions/5572
What’s in this release
- Helm-controller fixes: resolves a post-renderer conflict between overlapping hooks and templates, and now ignores force replace when server-side apply is enabled (helm-controller v1.5.4).
- Notification-controller fixes: restores forwarding of commit status events for generic providers and tightens GCR Receiver verification by requiring the audience field (will become mandatory in Flux v2.9) (notification-controller v1.8.4).
- Kustomize and source improvements: adds the MigrateAPIVersion feature gate for migrating resource API versions in managed fields, and upgrades go-git to v5.18.0 to improve Git operation performance (kustomize-controller v1.8.4, source-controller v1.8.3, image-automation-controller v1.1.2).
Upgrade notes
- Follow the Upgrade Procedure for Flux v2.7+ when moving from v2.6: https://github.com/fluxcd/flux2/discussions/5572.
- Ensure any GCR Receiver secret includes the audience field before upgrading; the audience requirement will be mandatory in Flux v2.9. If you need to revert, the previous release is v2.8.5.
Share your experience with the upgrade or report issues on the project’s GitHub — feedback helps spot regressions and edge cases early.
