Flux v1 to v2 migration and support timetable.
Flux Legacy has reached end of life.
Flux Legacy and Helm Operator have been archived.
We strongly recommend you familiarise yourself with the newest Flux and migrate as soon as possible.
|Date||Flux 1||Flux 2 CLI||GOTK1|
|Oct 6, 2020||Maintenance Mode||Development Mode||All Alpha2|
|Feb 18, 2021||Partial Migration Mode||Feature Parity||Image Automation Alpha. All others reached Feature Parity, Beta|
|June 30, 2021||Superseded||Needs further testing, may get breaking changes||All Beta, Production Ready3|
|May 1, 2022||Migration and security support only||Beta, Production Ready||All Beta, Production Ready|
|November 1, 2022||Archived||Public release candidate, Production Ready||All stable, Production Ready|
GOTK is shorthand for the GitOps Toolkit APIs and Controllers ↩︎
Versioning: Flux 2 is a multi-service architecture, so requires a more complex explanation than Flux 1:
- Flux 2 CLI follows Semantic Versioning scheme
- The GitOps Toolkit APIs follow the Kubernetes API versioning pattern. See Roadmap for component versions.
- These are coordinated for cross-compatibility: For each Flux 2 CLI tag, CLI and GOTK versions are end-to-end tested together, so you may safely upgrade from one MINOR/PATCH version to another.
The GOTK Custom Resource Definitions which are at
v2beta2and their controllers are considered stable and production ready. Going forward, breaking changes to the beta CRDs will be accompanied by a conversion mechanism. ↩︎
Last modified 2022-10-24: Update wording and docs for v1 archival (c9e57b3)