GitOps and Kubernetes delivery
What is Flux? An introduction to the Flux Project's GitOps delivery tools for Kubernetes
Flux is a set of open and extensible continuous and progressive delivery solutions for Kubernetes. It is a CNCF Graduated GitOps project. The desired state of a system, including apps and configuration, is described in Git, and Flux syncs changes automatically.
- Tool
- Flux
- Made by
- Flux Project
- Official site
- fluxcd.io
- Category
- GitOps and Kubernetes delivery
Who makes Flux
Flux is developed by the Flux Project. It is a vendor-neutral CNCF project maintained by volunteers. The official website is linked below this article.
Official website: fluxcd.io
What Flux is for
Flux keeps a Kubernetes cluster in line with what is declared in Git. Apps and configuration are described there, and Flux reconciles the cluster toward that description automatically. Because changes are synced this way, kubectl is not needed to apply them.
Flux enables application deployment. Together with Flagger, it also enables progressive delivery through the same automatic reconciliation.
Who Flux is for
The project names Kubernetes admins and app developers, as well as platform teams, as its audience.
Its pull-based model and support for multiple Git repositories and multi-cluster management are relevant to teams that run Kubernetes for several users or workloads.
Notable capabilities
Flux covers sources, delivery, security and supply-chain practices. The capabilities below are the ones documented by the project.
- Git as the source of truth: desired state for apps and configuration lives in Git, and changes sync automatically.
- Automated image updates: Flux can push back to Git when container images are updated.
- Flexible sources: it works with major Git providers, container registries, and S3-compatible buckets.
- Kubernetes RBAC: it uses RBAC via impersonation and supports multiple Git repositories.
- Multi-cluster management: this works with Cluster API.
- Templating and policy: it supports Kustomize and Helm, plus policy-driven validation such as OPA and Kyverno.
- Pull-based security: it follows a pull-based security model with least privileges.
- Signed releases: the Flux CLI and controller images are signed using Sigstore Cosign and GitHub OIDC, and an SBOM in SPDX format is published with each release.
- SLSA: from version 2.0.0, Flux provisionally meets SLSA Build Level 3.
How Flux fits GitOps and Kubernetes delivery
Flux is the GitOps engine in this category. It handles the step after a build: getting declared state from Git, registries or buckets into a cluster and keeping it there. It does not replace build tooling, so it sits alongside continuous integration systems.
In Deployelm's wider niche of CI/CD and deployment platforms, Flux covers the continuous delivery side for Kubernetes. Progressive delivery is available by pairing it with Flagger. Its signed images, published SBOMs and SLSA status make it relevant where software supply chain practices matter.
Frequently asked questions
What is Flux used for?
Flux deploys applications to Kubernetes from state described in Git. Changes are synced automatically, so kubectl is not needed.
Who develops Flux?
Flux is developed by the Flux Project. It is a vendor-neutral CNCF project maintained by volunteers.
Does Flux support Helm and Kustomize?
Yes. Flux supports Kustomize and Helm, and also policy-driven validation such as OPA and Kyverno.
Does Flux support progressive delivery?
Yes, with Flagger. Flux enables progressive delivery through automatic reconciliation when combined with Flagger.
Is Flux a CNCF project?
Yes. Flux is a CNCF Graduated project.
Deployelm is independent and is not affiliated with Flux Project. Product names belong to their owners. Features change; confirm details on the official website.