We are retiring Cluster Configuration with Flux v1 on 24th May, 2025 – transition to GitOps extension for Kubernetes to move to Flux v2
Published date: 17 March, 2023
On 24th May, 2025, we will retire Cluster Configuration Service that uses Flux v1. Please migrate to GitOps Extension to deploy Flux v2 configuration before that date.
Microsoft managed GitOps extension is built on Flux v2 open-source components. This extension is available to both Arc enabled Kubernetes clusters and Azure Kubernetes Clusters. The service can be configured directly per-cluster, or at-scale orchestrated by Azure Policy.
Key benefits of using GitOps extension with Flux v2
-
Flux v1 is a monolithic do-it-all operator; Flux v2 separates the functionalities into specialised controllers, collectively called the GitOps Toolkit. The toolkit contains the following core components: Source Controller, Kustomize Controller, Helm Controller and Notification Controller.
-
Supports synchronisation with multiple source repositories.
-
Supports multi-tenancy, like applying each source repository with its own set of permissions
-
Operational insight through health checks, events, and alerts
-
Supports Git branches, pinning on commits and tags, follow SemVer tag ranges
-
Credentials config per GitRepository resource: SSH private key, HTTP/S username/password/token, OpenPGP public keys
Beginning 1st May, 2023, you will no longer be able to create Flux v1 based Cluster Configuration resources. All resources created before May 2023 will be supported through 24th May, 2025. During this period, there will not be any new feature updates to Cluster Configuration service. The open-source project of Flux v1 was moved to the public archive on 1st November, 2022.
Required action
Follow the steps in the migration guidance to transition to GitOps Extension for Flux v2 by 24th May, 2025. You can review pricing details here, there is no change in pricing from Flux v1 to Flux v2.
Help and support
If you have questions, get answers from community experts in Microsoft Q and A. If you have a support plan and you need technical help, create a support request.