Flux | v2.8.5

Flux v2.8.5 released on 07-04-2026


Flux v2.8.5 is out now. A patch release delivering bug fixes and small improvements across Flux controllers to improve reconciliation reliability, storage behaviour and receiver configuration.

See the Flux GitHub release notes and component changelogs for full details, and follow the published upgrade procedure when moving from v2.6 to v2.7+: https://github.com/fluxcd/flux2/discussions/5572

What’s in this release

  • kustomize-controller v1.8.3: fixes a race condition where a cancelled reconciliation could leave stale data in the cache and cause Kustomizations to get stuck.
  • source-controller v1.8.2: fixes Azure Blob prefix not being passed to the storage client and improves the error message for encrypted SSH keys without a password.
  • notification-controller v1.8.3: adds optional email and audience fields to the GCR Receiver for tighter verification and includes an Azure Event Hub managed identity provider manifest example.

Upgrade notes

  • If you are upgrading from v2.6, follow the Upgrade Procedure for Flux v2.7+ to ensure a smooth transition: https://github.com/fluxcd/flux2/discussions/5572
  • To roll back, reapply the previous release tag (for example v2.8.4) as needed; consult the full changelog for component versions and changes: https://github.com/fluxcd/flux2/compare/v2.8.4…v2.8.5

Try the update and share any comments or issues on the Flux GitHub — feedback helps catch edge cases and improves stability for everyone.

Related posts

Agentic AI still needs domain judgement

Agentic AI can write the thing, but it still cannot tell you whether the thing is right. That is where domain expertise matters, because a clean config or neat bit of glue logic can still be wrong in...

Weekly Tech Digest | 06 Jul 2026

Stay updated with the latest in tech! This digest covers AI ethics, auto industry shifts, and the impact of politics on technology, exploring today's pressing issues.

wolfCOSE zero-allocation parsing in embedded C

wolfCOSE looks sensible only if you care about what your firmware actually has to carry. I like that, because on small targets the wrong crypto feature can cost more than the message itself, and there...