The GitOps Kubernetes operator
Announcement Flux has joined CNCF as a sandbox project
We believe in GitOps:
- You declaratively describe the entire desired state of yoursystem in git. This includes the apps, config, dashboards,monitoring and everything else.
- What can be described can be automated. Use YAMLs to enforceconformance of the system. You don’t need to run
kubectl, all changes gothrough git. Use diff tools to detect divergence between observed anddesired state and get notifications.
- You push code not containers. Everything is controlled throughpull requests. There is no learning curve for new devs, they just useyour standard git PR process. The history in git allows you to recoverfrom any snapshot as you have a sequence of transactions. It is muchmore transparent to make operational changes by pull request, e.g.fix a production issue via a pull request instead of making changes tothe running system.
Flux is a tool that automatically ensures that the state of a clustermatches the config in git. It uses an operator in the cluster to triggerdeployments inside Kubernetes, which means you don’t need a separate CD tool.It monitors all relevant image repositories, detects new images, triggersdeployments 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, everychange is atomic and transactional, git has your audit log. Each transactioneither fails or succeeds cleanly. You’re entirely code centric and don’t neednew infrastructure.
What Flux does
Flux is most useful when used as a deployment tool at the end of aContinuous Delivery pipeline. Flux will make sure that your newcontainer images and config changes are propagated to the cluster.
Who is using Flux in production
- ABA English
- ArangoDB Oasis
- Babylon Health
- CLVR Cloud Ltd
- College of William & Mary
- Control Plane
- Crowd Riff
- IBM Cloudant
- Improwised Technologies
- karriere tutor GmbH
- Sage AI Labs
- Under Armour
- Walmart Chile
- Weave Cloud
- Working Group Two
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 veryclosely coupled to that of WeaveCloud. Over the years the communityaround Flux grew, the numbers of integrations grew andthe team started the process of generalising the code, so that more projectscould easily integrate.
Get started with Flux
With the following tutorials:
or just browse through the documentation.
Do you want to release your Helm charts in a declarative way?Take a look at the
As Flux is Open Source, integrations are very straight-forward. Here area few popular ones you might want to check out:
- Manage a multi-tenant cluster with Flux and Kustomize
- Managing Helm releases the GitOps way
- OpenFaaS GitOps workflow with Flux
- GitOps for Istio Canary deployments
- Fluxcloud to receive events from Flux
Community & Developer information
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 ofConduct.
Instances of abusive, harassing, or otherwise unacceptable behaviormay be reported by contacting a Flux project maintainer, or the CNCFmediator, Mishi Choudhary email@example.com.
To familiarise yourself with the project and how things work, you mightbe interested in the following:
If you have any questions about Flux and continuous delivery:
- Read the Flux docs.
- Invite yourself to the CNCF communityslack and ask a question on the #fluxchannel.
- To be part of the conversation about Flux’s development, join theflux-dev mailing list.
- File an issue.
Your feedback is always welcome!
To restore the repository download the bundle
git clone fluxcd-flux_-_2019-12-03_00-04-35.bundle