💖 Flux Migration CommitmentThis public timetable clarifies our commitment to end users. Its purpose is to help improve your experience in deciding how and when to plan infra decisions related to Flux versions. Please refer to the Roadmap for additional details.
|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|
|TBD||Migration and security support only||Public release (GA), Production Ready||All Beta, Production Ready|
|TBD||Archived||Continued active development||Continued active development|
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
v2beta1and their controllers are considered stable and production ready. Going forward, breaking changes to the beta CRDs will be accompanied by a conversion mechanism. ↩︎