The GitOps Kubernetes operator
On Flux v2 In an announcement in August 2019, the expectation was set that the Flux project would integrate the GitOps Engine, then being factored out of ArgoCD. Since the result would be backward-incompatible, it would require a major version bump: Flux v2.
After experimentation and considerable thought, we (the maintainers) have found a path to Flux v2 that we think better serves our vision of GitOps: the GitOps Toolkit. In consequence, we do not now plan to integrate GitOps Engine into Flux.
:warning: This also means that Flux v1 is in maintenance mode.
We believe in GitOps:
kubectl, all changes go through git. Use diff tools to detect divergence between observed and desired state and get notifications.
Flux is a tool that automatically ensures that the state of a cluster matches the config in git. It uses an operator in the cluster to trigger deployments inside Kubernetes, which means you don't need a separate CD tool. It monitors all relevant image repositories, detects new images, triggers deployments and updates the desired running configuration based on that (and a configurable policy).
The benefits are: you don't need to grant your CI access to the cluster, every change is atomic and transactional, git has your audit log. Each transaction either fails or succeeds cleanly. You're entirely code centric and don't need new infrastructure.
Flux is most useful when used as a deployment tool at the end of a Continuous Delivery pipeline. Flux will make sure that your new container images and config changes are propagated to the cluster.
Our list of production users has moved to https://fluxcd.io/adopters/#flux-v1.
If you too are using Flux in production; please submit a PR to add your organization to the list!
In the first years of its existence, the development of Flux was very closely coupled to that of Weave Cloud. Over the years the community around Flux grew, the numbers of integrations grew and the team started the process of generalising the code, so that more projects could easily integrate.
With the following tutorials:
or just browse through the documentation.
As Flux is Open Source, integrations are very straight-forward. Here are a few popular ones you might want to check out:
We welcome all kinds of contributions to Flux, be it code, issues you found, documentation, external tools, help and support or anything else really.
The Flux project adheres to the CNCF Code of Conduct.
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting a Flux project maintainer, or the CNCF mediator, Mishi Choudhary [email protected].
To familiarise yourself with the project and how things work, you might be interested in the following:
Reminder that Flux v1 is in maintenance mode. If you have any questions about Flux v2 and future migrations, these are the best ways to stay informed:
If you have further questions about Flux or continuous delivery:
Your feedback is always welcome!