← ← Back to all products
Flux
Active
DevOps & CI/CD Latest Version: 2.7.5 Latest Release: Nov 27, 2025
Flux is a set of continuous delivery solutions for Kubernetes using GitOps principles.
Versions
9
Latest Version
2.7.5
Active Support
3
EOL
6
Lifecycle Timeline
Today ↓
2.7
2.7
2.6
2.6
2.5
2.5
2.4
2.4
2.3
2.3
2.2
2.2
2.1
2.1
2.0
2.0
1.25
1.25
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 2.7 | Sep 30, 2025 | - | No | 2.7.5 | No | Active |
| 2.6 | May 29, 2025 | - | No | 2.6.4 | No | Active |
| 2.5 | Feb 20, 2025 | - | No | 2.5.1 | No | Active |
| 2.4 | Sep 30, 2024 | - | Sep 30, 2025 | 2.4.0 | No | EOL |
| 2.3 | May 13, 2024 | - | May 29, 2025 | 2.3.0 | No | EOL |
| 2.2 | Dec 12, 2023 | - | Feb 20, 2025 | 2.2.3 | No | EOL |
| 2.1 | Aug 24, 2023 | - | Sep 30, 2024 | 2.1.2 | No | EOL |
| 2.0 | Jul 5, 2023 | - | May 13, 2024 | 2.0.1 | No | EOL |
| 1.25 | Mar 30, 2022 | - | Nov 2, 2022 | 1.25.4 | No | EOL |
Frequently Asked Questions
Which versions of Flux have reached end of life?
The following Flux versions have reached end of life and no longer receive security updates: 2.4, 2.3, 2.2, 2.1, 2.0, 1.25. It is recommended to upgrade to a supported version.
Is it safe to continue using Flux 2.4?
Flux 2.4 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Flux?
The latest version of Flux is 2.7.5, released in the 2.7 release cycle.
How many versions of Flux are currently supported?
Flux currently has 3 actively supported version(s): 2.7, 2.6, 2.5.
When does Flux 2.7 reach end of life?
Flux 2.7 does not have a specific end-of-life date announced yet.
What should I do when Flux reaches end of life?
When a Flux version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.