Flux is the CNCF-graduated GitOps toolkit for Kubernetes, maintained by Weaveworks alumni and adopted by Deutsche Telekom, State Farm, and D2iQ. The other major GitOps engine alongside Argo CD.
Source: GitHub · fetched 2026-04-17
Flux v2 is a set of Kubernetes controllers that implement GitOps—reconciling cluster state against Git, OCI, or Helm repositories. The first generation was released in 2016 by Weaveworks, and v2 shipped in 2020 as a rewrite built on the GitOps Toolkit: a collection of composable controllers (source-controller, kustomize-controller, helm-controller, notification-controller, image-reflector-controller) that can be used independently.
Flux is Apache 2.0 licensed and a CNCF graduated project. Its model emphasizes being a toolkit rather than an application—there is no default UI, which pushes teams toward integrations like Weave GitOps, Capacitor, or the Flux Terraform provider. It is a closer fit for teams that want strict GitOps with minimal in-cluster UI footprint.
Public Flux adopters include Deutsche Telekom, State Farm, D2iQ, SAP, Axel Springer, Replicated, and Volkswagen. It is the default GitOps engine inside several managed Kubernetes platforms—Azure Arc-enabled Kubernetes ships Flux, as do some of Weaveworks' historical enterprise customers.
Flux users are platform engineers who favor a composable toolkit, SREs who want opinionated reconcilers with minimal UI surface, and teams that already run Helm at scale. These personas buy the same cloud-native stack as Argo CD shops: registries, secret managers, policy engines, image scanners, and progressive-delivery tools.
According to the Flux README: “Flux is a tool for keeping Kubernetes clusters in sync with sources of configuration (like Git repositories) and automating updates to configuration when there is new code to deploy.” (source)
If you sell a tool that integrates with Flux, complements it, or competes with it, the developers contributing to it are your buyers. They're the ones evaluating tools in your category right now.
Developers signal interest through GitHub activity—starring, forking, opening issues, submitting pull requests. LeadCognition captures those signals across millions of repositories and enriches each developer with verified work email, LinkedIn URL, and current employer.
Drop any GitHub repo into LeadCognition and get a ranked list of developers actively engaging with it—with emails, not just usernames.
See developers using Flux → Start freeIf you're researching Argo CD, you're probably also looking at:
Flux is used in production at SAP, Xero, Giant Swarm, and hundreds of platform teams running fully automated GitOps deployments on Kubernetes clusters.
Flux is a CNCF graduated project maintained by the Flux community and the fluxcd organization on GitHub. Major corporate contributors include Weaveworks (creators), Microsoft, and Red Hat.
Argo CD (the other dominant CNCF GitOps operator), Jenkins X, Spinnaker, and traditional CI/CD pipelines using GitHub Actions or GitLab CI. Flux and Argo CD are the two most widely deployed GitOps solutions for Kubernetes.
Flux has 204 contributors (GitHub, 2026/04). It is one of the more actively contributed open-source projects in its category, with contributions from both individual developers and corporate engineering teams.
Yes. Flux is production-ready: it has 8.1k GitHub stars, 204 contributors (GitHub, 2026/04), and is last released Apr 2026. It is used in production at large-scale organizations and has a mature release cadence.
Drop a GitHub repo. Get a ranked list of developers with verified emails, employers, and the signal that triggered them. Start with 25 free unlocks.
Start free — 25 developer signals on usNo credit card required. Self-serve. Transparent pricing.