Flux Version History

3 active, 7 end-of-life. 10 versions tracked.

Flux CD releases minor versions roughly monthly, following a rapid iteration cycle. As a CNCF graduated project, Flux is the leading GitOps operator for Kubernetes alongside Argo CD.

Recommendation

For GitOps on Kubernetes, use Flux 2.x (latest). Flux v1 is end-of-life and should not be used for new deployments.

Version Released End of Life Latest Patch Status
Flux 2.8 February 24, 2026 TBD 2.8.1 Active
Flux 2.7 September 30, 2025 TBD 2.7.5 Active
Flux 2.6 May 29, 2025 TBD 2.6.4 Active
Flux 2.5 February 20, 2025 February 24, 2026 2.5.1 End of Life
Flux 2.4 September 30, 2024 September 30, 2025 2.4.0 End of Life
Flux 2.3 May 13, 2024 May 29, 2025 2.3.0 End of Life
Flux 2.2 December 12, 2023 February 20, 2025 2.2.3 End of Life
Flux 2.1 August 24, 2023 September 30, 2024 2.1.2 End of Life
Flux 2.0 July 5, 2023 May 13, 2024 2.0.1 End of Life
Flux 1.25 March 30, 2022 November 2, 2022 1.25.4 End of Life
View Flux Hub Page →

Flux Support Policy

The Flux community supports the latest release with patches. Older versions are superseded and receive no backported fixes. Given the monthly release cadence, staying current is expected.

What You Need to Know

Flux v1 is end-of-life. If you're still on it, migrate to Flux v2 (completely different architecture).

Flux v2 is built on the GitOps Toolkit, a set of composable APIs for building GitOps workflows.

Flux supports OCI artifacts as sources, letting you store Helm charts and Kustomize overlays in container registries.

Flux includes built-in drift detection, automatically reconciling cluster state with your Git repository.

Frequently Asked Questions

How do I migrate from Flux v1 to v2?
Flux v2 is a complete rewrite, not an upgrade from v1. You need to install Flux v2 alongside v1, migrate your repositories and Kustomizations, verify reconciliation works, then remove v1. The Flux team provides a migration guide.
How often does Flux release new versions?
Flux ships minor versions roughly monthly. Patch releases come out as needed. The project moves fast, and staying on the latest version is strongly recommended.
Should I use Flux or Argo CD?
Flux is more lightweight and composable, better for teams that want fine-grained control over their GitOps pipeline. Argo CD has a richer UI and is better for teams that want a visual dashboard for application deployments. Both are CNCF graduated projects with strong communities.

Related Tools

K8s Deprecation Checker
Vulnerability Scanner
EOL Timeline Visualizer

Get Flux release alerts

New releases, EOL warnings, security patches. Monthly digest, no spam.

Free forever. Unsubscribe anytime.