CI/CD
Flux CD Releases
Track every Flux CD release, from latest stable to end-of-life. Version timelines, EOL dates, security patches, and upgrade guidance for GitOps teams.
—
Total Versions
—
Supported
—
Latest
Version Timeline
All tracked releases with lifecycle status and EOL dates.
Loading version data…
Embed Badges
Add live Flux CD status badges to your README, docs, or dashboard.
Health Status
Overall support health
EOL Countdown
Next end-of-life date
Latest Version
Current stable release
CVE Status
Known vulnerabilities
Frequently Asked Questions
Common questions about Flux CD releases and lifecycle.
How often does Flux CD release new versions?
Flux CD ships minor releases roughly every 2-3 months. Patch releases with bug fixes and security updates ship as needed.
How long are Flux CD versions supported?
Flux typically supports the last two or three minor releases. Older versions stop receiving security patches and should be upgraded.
What is the difference between Flux v1 and Flux v2?
Flux v2 is a complete rewrite using a set of Kubernetes controllers (source-controller, kustomize-controller, helm-controller, notification-controller). Flux v1 is deprecated and should not be used for new deployments.
Should I use Flux CD or Argo CD?
Both are CNCF graduated GitOps tools. Flux is more modular and infrastructure-focused, using Kubernetes-native CRDs. Argo CD provides a richer UI and application-centric model. Teams that prefer declarative, controller-based workflows often choose Flux.