3 years ago

Category: Software, Kubernetes

The Flux project has moved on to the incubation tier of the Cloud Native Computing Foundation (CNCF), bringing its unique form of continuous delivery to the foundation’s second tier of project maturity. While Flux bills itself as a continuous delivery tool, it also flips the script for traditional definitions of continuous delivery, with Flux creator and maintainer Michael Bridgen crediting Flux as being “the project that gave rise to ‘GitOps’.”

Weaveworks Chief Technology Officer Cornelia Davis credits Kubernetes as really shifting this paradigm, with its declarative model, and Flux similarly practices a reconciliation-based form of continuous delivery and operations.

One of the things that was a bit of a game-changer for Flux is this notion of a reconciliation-based way of doing continuous delivery.

Flux itself is building up the suite of controllers that serve the continuous delivery and continuous operations needs, so you’ll start to see a suite of controllers, as well as tooling that allows us to stitch those controllers together into these continuous delivery and continuous operations pipelines that we call GitOps pipelines.”