CNCF promoted GitOps Flux to be a Incubated Project.

CNCF had earlier promoted the Flux project from Sandbox to Incubator. This demonstrates not only the breadth of the Flux application, but also the fact that it joins the Family of GitOps projects, bringing a unified toolkit approach to continuous delivery.

Flux users handle continuous and incremental delivery of Kubernetes.

Flux helps developers, operators, and platform engineers maintain a single source of truth for their declarative infrastructure and deployment configurations, following the principles of GitOps. Flux monitors Git for changes to what is running on Kubernetes and updates the cluster accordingly.

Flux consists of the GitOps Toolkit and Flagger. The GitOps Toolkit is a set of apis and Kubernetes controllers that make up Flux’s running time. The toolkit can be used to extend Flux and build your own continuous delivery system; Flagger is A Kubernetes operations tool that handles progressive delivery, including Canary, A/B testing, and Blue/Green deployment.

The program is already popular, with more than 80 organizations using it in production, including Fidelity Investments, Starbucks, and Canva.

“GitOps started with a simple idea of using Git as a source of truth for a declarative infrastructure, and has evolved into an ecosystem of tools that improve the developer experience of delivering applications using Kubernetes,” said Chris Aniszczyk, CTO of CNCF. As more organizations adopt cloud-native software at scale, GitOps tools like Flux will naturally be adopted, and we look forward to nurturing their communities within CNCF.”

CNCF plans to discontinue Flux V1 by the end of 2021. According to the project roadmap, Flux V2 will be released in a GA version in a few months.

Flux V2 integrates with Prometheus, Helm, and other components of the Kubernetes ecosystem. In addition, it includes a software development kit (SDK) and supports synchronization of any number of Git repositories.

Viktor Farcic, a Member of Google Developer Experts and Docker Universal Groups, likes the GitOps concept and thinks Flux V2 is a big improvement over V1: “First, Flux initially made no attempt to provide any declarative definition for the installation, at least not on the original installation page. There was no attempt to get us to define something as code and store it in Git before applying it to a cluster. This all changed when Flux V2 was introduced, which changed the installation process and now creates a Git repo that pushes the Flux manifest before installing Flux. From then on, any changes to Flux can be made by changing the associated repositories. For that, Flux did a great job!”

Note: For a CNCF project to move from sandbox to incubation, it must be used in production by at least three independent end-user companies, have a significant number of committers, and have at least one publicly referenced implementation. Any CNCF project that is promoted to the incubation stage must undergo a rigorous review process to ensure that it is stable and production-ready.