Flux CD
a CNCF project, originally by Weaveworks
Flux CD (Flux) is an open-source, CNCF-graduated GitOps toolkit for Kubernetes that continuously reconciles cluster state with configuration stored in Git repositories or other sources like OCI registries and Helm repositories, applying…
Definition
Flux CD (Flux) is an open-source, CNCF-graduated GitOps toolkit for Kubernetes that continuously reconciles cluster state with configuration stored in Git repositories or other sources like OCI registries and Helm repositories, applying changes automatically as they're committed.
Overview
Flux originated at Weaveworks, whose founders coined the term 'GitOps' around 2017, and was later rearchitected as 'Flux2' — a modular set of Kubernetes controllers collectively called the GitOps Toolkit — before being donated to and graduating within the CNCF. Rather than a single monolithic application, Flux is composed of specialized controllers, each responsible for one concern: the Source Controller fetches artifacts from Git, Helm repositories, S3-compatible buckets, or OCI registries; the Kustomize Controller applies Kustomize-based manifests; the Helm Controller manages Helm releases; the Notification Controller handles alerts and webhook-based event triggers; and the Image Automation Controller can detect new container image versions and automatically commit updated manifests back to Git. This composable, API-driven design makes Flux well suited to being extended or integrated into custom platform engineering setups, since each controller exposes Kubernetes custom resources that can be orchestrated independently or combined. Flux emphasizes a 'pull' reconciliation loop similar to Argo CD: controllers running in-cluster continuously compare live state to the declared state in the source repository and converge toward it, self-healing any manual or out-of-band changes. Flux is commonly used with Flagger, a companion progressive delivery tool for automated canary, blue-green, and A/B deployment strategies with metric-based analysis, filling a role analogous to Argo Rollouts in the Argo ecosystem. Compared to Argo CD, Flux has historically been positioned as more lightweight, CLI/API-first, and composable, without a built-in web UI by default (though Weaveworks and later projects have offered UI layers), appealing to teams that want to assemble GitOps functionality into a broader custom platform rather than adopt an all-in-one application.
Key Features
- Modular GitOps Toolkit: separate controllers for source fetching, Kustomize, Helm, notifications, and image automation
- Pulls configuration from Git, Helm repositories, OCI registries, or S3-compatible buckets
- Continuous reconciliation loop that self-heals drift from the declared state
- Image Automation Controller can auto-commit new image tags back to Git
- CNCF graduated project with roots in Weaveworks, who coined the term 'GitOps'
- API-first and composable, designed to integrate into custom platform engineering stacks
- Pairs with Flagger for automated progressive delivery (canary, blue-green, A/B)
- No mandatory built-in web UI, unlike Argo CD's default dashboard
Use Cases
Alternatives
History
Flux is a GitOps continuous-delivery tool for Kubernetes that keeps a cluster reconciled to configuration stored in Git. Its initial commit was made on July 7, 2016, by Peter Bourgon at Weaveworks, whose team built Flux for predictable internal deployments — and whose accompanying writing coined the term "GitOps," framing operations as changes made through pull requests. Weaveworks donated Flux to the Cloud Native Computing Foundation in 2019 (incubating), and in 2020–2021 the project was redesigned from the ground up as Flux v2, built on Kubernetes controller-runtime and custom resources and componentized into the "GitOps Toolkit." Flux graduated within the CNCF in 2022, alongside peers like Kubernetes, Helm, and Argo.
Sources
- Flux — official website · as of 2026-07-17
- CNCF — "What is Flux CD?" · as of 2026-07-17