Flux
0 comparisons available
About Flux
Flux is an open-source GitOps toolkit for Kubernetes continuous delivery, created by Weaveworks in 2019 as Flux v2 (a complete rewrite of the original Flux v1) and graduated as a CNCF project in 2022. Flux implements GitOps via a set of composable Kubernetes controllers — Source Controller (watches Git repos, Helm repos, S3 buckets), Kustomize Controller (applies Kustomize manifests), Helm Controller (manages Helm releases), Notification Controller (alerts on events), and Image Reflector/Update Controllers (automate image tag updates). Flux's CLI-first, CRD-native design makes it composable: each controller is independently deployable and can be used without the others. Flux's GitRepository CRD defines a Git source; HelmRelease CRD defines a Helm deployment; Kustomization CRD applies a directory of manifests — together they cover the full GitOps deployment surface. Flux's progressive delivery integrations (Flagger, developed by Weaveworks) add canary deployments, blue/green, and A/B testing with Istio, Linkerd, NGINX, or Traefik as traffic controllers. Flux multi-tenancy allows namespace-scoped Flux instances for different teams with RBAC isolation. Flux Bootstrap sets up a cluster with Flux and commits the generated manifests back to Git in a single command, following GitOps principles from day one. Flux is used at Deutsche Telekom, Volvo, and most Weaveworks customers. Weaveworks' closure in 2024 raised community concerns about Flux's stewardship, but the CNCF and active maintainer community provide ongoing governance. FluxCD.io remains one of the two dominant GitOps tools alongside Argo CD.
Frequently Asked Questions
Flux vs Argo CD — which GitOps tool is better?
Argo CD for teams wanting UI-rich multi-cluster management, ApplicationSets for large fleets, and the broader Argo ecosystem (Rollouts, Workflows). Flux for teams wanting a minimal, composable CLI-first approach, stronger Helm Controller integration, and a pure GitOps philosophy without a heavy control plane. Both are CNCF graduated and production-ready. Argo CD has broader enterprise adoption; Flux is favored by GitOps purists.
Is Flux still maintained after Weaveworks closed?
Yes — Flux is a CNCF graduated project maintained independently of Weaveworks. When Weaveworks closed in February 2024, the CNCF confirmed continued stewardship with an active maintainer community from multiple organizations. The project remains in active development and the FluxCD.io governance is CNCF-governed, not Weaveworks-dependent. Teams evaluating Flux should check the current release cadence at github.com/fluxcd/flux2.
What is Flagger and how does it relate to Flux?
Flagger is a Kubernetes progressive delivery operator developed by Weaveworks that integrates with Flux. Flagger automates canary deployments: it gradually shifts traffic to a new version, runs automated analysis (success rate, latency, custom metrics), and either promotes or rolls back based on results. Flagger works with Istio, Linkerd, AWS App Mesh, NGINX, Traefik, and Gloo as traffic controllers. Flux manages the base deployment; Flagger handles the progressive rollout strategy.
Top Alternatives to Flux
ArgoCD
UI-rich GitOps CD — larger community, ApplicationSets, multi-cluster UI vs Flux's CLI-first approach
Jenkins
Push-based CI/CD — traditional alternative; Flux implements pull-based GitOps model
GitHub Actions
CI and push-based deployment — Actions builds; Flux handles GitOps K8s sync
Helm
Kubernetes packaging — Flux's Helm Controller manages Helm releases as GitOps artifacts
Kustomize
Kubernetes configuration management — Flux's Kustomize Controller applies Kustomize overlays declaratively
Tekton
Kubernetes-native CI pipeline — Tekton builds; Flux deploys via GitOps sync
No comparisons found for Flux yet.
Search for a comparison