GitOps for k8s
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Alfonso Acosta 876f994ac2
Merge pull request #2627 from fluxcd/release/1.16.0
10 months ago
.circleci Republish release tag with v prefix 11 months ago
.github Add short quality checklist to pull request templ 11 months ago
bin Upgrade `kubeyaml` to `0.7.0` 1 year ago
chart Merge pull request #2532 from at-ishikawa/update-readme 10 months ago
cmd Remove `Info.CreatedTS` method 10 months ago
deploy Bump Flux image tag version 10 months ago
docker bump alpine to 3.10 10 months ago
docs fix indent in the .flux.yaml reference 10 months ago
integrations Move Flux packages to pkg dir 1 year ago
internal_docs Improve phrasing for adding changelog entry 10 months ago
pkg Bump Flux image tag version 10 months ago
snap Build: upgrade Go to `1.13.1` 11 months ago
test/e2e Fix patchFile-based manifest generation 10 months ago
.gitignore Update .gitignore 10 months ago
.readthedocs.yml rename site/ to docs/ 1 year ago Add 1.16.0 entry to 10 months ago Move code of conduct into its own file. 2 years ago Update org name in error help, other docs 1 year ago
DCO docs: steal and DCO docs from scope, modify slightly 2 years ago
LICENSE Initial commit 4 years ago
MAINTAINERS Update Slack information in MAINTAINERS file 1 year ago
Makefile e2e: Add missing dependency on fluxctl 10 months ago added cybrary as a prod user of flux 10 months ago
go.mod remove replace directives 10 months ago
go.sum remove replace directives 10 months ago
tools.go Remove `` from go.mod 1 year ago


Announcement Flux has joined CNCF as a sandbox project

We believe in GitOps:

  • You declaratively describe the entire desired state of your system in git. This includes the apps, config, dashboards, monitoring and everything else.
  • What can be described can be automated. Use YAMLs to enforce conformance of the system. You don’t need to run kubectl, all changes go through git. Use diff tools to detect divergence between observed and desired state and get notifications.
  • You push code not containers. Everything is controlled through pull requests. There is no learning curve for new devs, they just use your standard git PR process. The history in git allows you to recover from any snapshot as you have a sequence of transactions. It is much more transparent to make operational changes by pull request, e.g. fix a production issue via a pull request instead of making changes to the running system.

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.

Deployment Pipeline

CircleCI GoDoc Documentation

What Flux does

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.

Who is using Flux in production

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.

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 fluxcd/helm-operator.


As Flux is Open Source, integrations are very straight-forward. Here are a few popular ones you might want to check out:

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 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

To familiarise yourself with the project and how things work, you might be interested in the following:

Getting Help

If you have any questions about Flux and continuous delivery:

Your feedback is always welcome!