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 65d11c6c79 Run dep ensure -update 10 months ago
.circleci Build and push on git tagging 11 months ago
.github Add tag filter for chart-* to GitGHub workflow 1 year ago
api Be more tolertant towards missing image manifests 10 months ago
bin Bump to kubeyaml 0.5.1 to fix (F)HR updating 1 year ago
chart Add chart only changes to change log 10 months ago
checkpoint making compiling work on raspberry pi's 1 year ago
cluster Fix `tag_all` pseudo policy on default-namespaced wokloads 11 months ago
cmd Reimplement --git-poll-interval in Helm operator 10 months ago
daemon Be more tolertant towards missing image manifests 10 months ago
deploy Fix typo 10 months ago
deploy-helm Update Helm operator manifests to '0.8.0' 10 months ago
docker Verify scanned keys in same build step as scan 10 months ago
errors Downgrade non-specific errors to application-level 2 years ago
event Revert renaming of serialized struct fields 1 year ago
git Cast error msg to lowercase to support Git 2.21 11 months ago
gpg Report keyfiles that were found but failed import 1 year ago
guid Make new subscriptions kick old subscriptions 3 years ago
http Revert all the renamings breaking the API 1 year ago
image Be more tolertant towards missing image manifests 10 months ago
integrations Adding chartFileRef option to valuesFrom. 10 months ago
internal_docs corrects mispelling 1 year ago
job Break dependencies among git, job, event packages 1 year ago
metrics Standardize http metrics, to flux_request_duration 3 years ago
policy Make `regex` an alias of `regexp` tag filter type 10 months ago
registry Fix typos 10 months ago
release Obtain scope of CRD instances from its manifest as a fallback 11 months ago
remote Be more tolertant towards missing image manifests 10 months ago
resource Rename resource method Policy() to Policies() 1 year ago
site Make `regex` an alias of `regexp` tag filter type 10 months ago
ssh Generate keys in a separate tmpfs volume 1 year ago
sync Simplify sync structures 1 year ago
test Use Helm operator image from build in e2e tests 10 months ago
update Fix typos 10 months ago
.gitignore Revert 11 months ago Add changelog entry for Helm operator v0.8.0 10 months ago Add changelog entry for flux 1.12.0 10 months ago Move code of conduct into its own file. 1 year ago update developing docs to remind to `make test` 1 year ago
DCO docs: steal and DCO docs from scope, modify slightly 1 year ago
Gopkg.lock Run dep ensure -update 10 months ago
Gopkg.toml Bump mergo to 0.3.7 10 months ago
LICENSE Initial commit 3 years ago
MAINTAINERS Add Slack handles to MAINTAINERS 1 year ago
Makefile Obsolete blank line 1 year ago document flux-dev mailing list 1 year ago
flux.go Admit "<cluster>" when parsing ResourceIDs 11 months ago
resourceid_test.go Admit "<cluster>" when parsing ResourceIDs 11 months ago


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

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.


Its major features are:

Relation to Weave Cloud

Weave Cloud is a SaaS product by Weaveworks that includes Flux, as well as:

  • a UI and alerts for deployments: nicely integrated overview, all Flux operations just a click away.
  • full observability and insights into your cluster: Instantly start using monitoring dashboards for your cluster, hosted 13 months of history, use a realtime map of your cluster to debug and analyse its state.

If you want to learn more about Weave Cloud, you can see it in action on its homepage.

Get started with Flux

Get started by browsing through the documentation below:


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.

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting a Flux project maintainer, or Alexis Richardson <>. Please refer to our code of conduct as well.

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!