Skip to content
GitOps

Flux CD Releases

Track Flux CD releases, Kubernetes compatibility, GitOps Toolkit component versions, and upgrade guidance. Feature evolution from v1 to v2, and Argo CD comparison context.

Official Site Documentation

—

Total Versions

—

Supported

—

Latest

Version Timeline

All tracked releases with lifecycle status and EOL dates.

Loading version data…

Lifecycle Timeline

Visual overview of active support and maintenance windows.

v1 (legacy)
2.0
2.1
2.2
2.3
2.4
2022 2023 2024 2025 2026 2027 2028
Active
Maint
Active
Maint
Active
Maint
Active
Maint
Active
Maint
Active
Maint
Active / LTS
Maintenance
Today

Upgrade Paths

Migration guidance between major versions — breaking changes, effort estimates, and tips.

Flux v1 Flux v2 High Difficulty
Est. 2-8 hours depending on number of sources/releases

Breaking Changes

  • Complete architecture rewrite — no migration path
  • All configuration must be recreated as v2 CRDs
  • No more annotations-based config
  • Separate controllers replace monolithic operator
  • Image automation is a separate opt-in controller
  • Notification system completely different

Migration Notes

Flux v1 is dead. There is no automated migration. You need to: install Flux v2, recreate your GitRepository/HelmRepository sources, recreate your Kustomization/HelmRelease resources, set up notifications, and remove the Flux v1 operator. Flux provides a migration guide but it is a manual process.

2.1/2.2 2.4 Low Difficulty
Est. 30-60 minutes

Breaking Changes

  • Some CRD API fields deprecated
  • OCI source handling improvements
  • Notification provider API updates
  • Drift detection behavior changes

Migration Notes

Run flux install to upgrade. The CLI handles CRD updates. Check for deprecated API fields in your custom resources with flux check. Most upgrades within v2 are seamless.

Version Risk Assessment

Evaluate risk factors before choosing a version for production.

Version EOL Risk CVE Risk Ecosystem Cloud Support Overall Recommended Action
Flux CD v1 (any) Critical Critical Dead None Critical EOL since Nov 2022 — full rewrite to v2 required
Flux CD 2.0/2.1 Critical High Unsupported None Critical Past EOL — no security patches
Flux CD 2.2 High Medium Unsupported Degrading High Past support — upgrade to 2.4
Flux CD 2.3 Medium Low Maintenance Full Medium Security-only — upgrade to 2.4 soon
Flux CD 2.4 None Low Active Full Low Current — recommended

Flux supports the latest 2 minor versions. v1 has been dead since Nov 2022. Assessed March 2026.

Flux v2 Feature Comparison

Side-by-side feature differences across major versions.

Feature 2.0 2.1 2.2 2.3 2.4
OCI artifact sources Stable Stable Enhanced Enhanced Enhanced
Helm drift detection Beta Stable Stable Enhanced Enhanced
Image automation Stable Stable Enhanced Enhanced Enhanced
Multi-tenancy Basic Improved Improved Enhanced Enhanced
SOPS/Age decryption Stable Stable Stable Stable Stable
Health assessments Basic Improved Improved Enhanced Enhanced
Git sharding No No Beta Stable Stable
K8s version support 1.25-1.28 1.26-1.29 1.27-1.30 1.28-1.31 1.29-1.32
Vertical scaling Basic Improved Improved Enhanced Enhanced

Embed Badges

Add live Flux CD status badges to your README, docs, or dashboard.

Health Status

Overall support health

Flux CD Health Status
![Flux CD Health Status](https://img.releaserun.com/badge/health/flux.svg)

EOL Countdown

Next end-of-life date

Flux CD EOL Countdown
![Flux CD EOL Countdown](https://img.releaserun.com/badge/eol/flux.svg)

Latest Version

Current stable release

Flux CD Latest Version
![Flux CD Latest Version](https://img.releaserun.com/badge/v/flux.svg)

CVE Status

Known vulnerabilities

Flux CD CVE Status
![Flux CD CVE Status](https://img.releaserun.com/badge/cve/flux.svg)

Frequently Asked Questions

Common questions about Flux CD releases and lifecycle.

What happened to Flux v1?
Flux v1 reached end of life in November 2022. It was a monolithic operator that watched Git repos and applied changes. Flux v2 is a complete rewrite using the GitOps Toolkit architecture: separate controllers for source, kustomize, helm, notification, and image automation. There is no migration tool; you must recreate your configuration using Flux v2 CRDs.
How does Flux versioning work?
Flux uses the "flux" CLI version (2.x) and separate API versions for each controller CRD (source.toolkit.fluxcd.io/v1, kustomize.toolkit.fluxcd.io/v1, etc.). The flux CLI version determines the controller versions bundled together. Minor updates ship roughly monthly. The project maintains the latest 2 minor versions with patches.
How does Flux compare to Argo CD?
Flux is more Kubernetes-native: everything is a CRD, there is no web UI (use the Weave GitOps dashboard separately), and it integrates tightly with kustomize and Helm natively. Argo CD provides a richer out-of-box experience with a built-in web UI, SSO, and RBAC. Flux is better for teams who want lightweight, composable GitOps. Argo CD is better for teams who want a full-featured dashboard. Both are CNCF graduated projects.
Which Kubernetes versions does Flux support?
Flux 2.x supports the last 3-4 Kubernetes minor versions. Flux 2.3+ supports K8s 1.28-1.31. The controllers use server-side apply (requires K8s 1.22+) and rely on CRD v1 (requires K8s 1.16+). In practice, running a supported K8s version ensures Flux compatibility.
What is the GitOps Toolkit?
The GitOps Toolkit is the set of composable controllers that make up Flux v2: Source Controller (watches Git/Helm/OCI repos), Kustomize Controller (applies kustomize manifests), Helm Controller (manages Helm releases), Notification Controller (handles alerts and webhooks), and Image Automation Controllers (update image tags in Git). Each controller can be used independently.
How do I upgrade Flux?
Run flux install or update the Flux Helm chart. Flux handles its own CRD upgrades during installation. Always read the release notes for breaking API changes. If a CRD API version changes (e.g., v1beta2 → v1), existing resources may need conversion. Use flux check to verify the installation health after upgrading.

Related Tools

Dep EOL Scanner

Check your dependencies for end-of-life packages.

Stack Health Scorecard

Get an overall health grade for your tech stack.

Release Index

Browse all tracked platforms and their release timelines.