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.
Daniel Holbach b5c374ed7c add empty changelog entries for the upcoming release 1 year ago
.circleci Remove the helm prefix from helm-op version 1 year ago
.github Add first attempt at a pull request template. 1 year ago
api Split off SortedImageInfos to enforce constraint 1 year ago
apis/ Annotate resources caused by a FluxHelmRelease 1 year ago
bin Build and upload Windows binary of fluxctl 1 year ago
chart Bump Helm chart version - includes Flux v1.7.0 and Flux Helm Operator v0.2.1 1 year ago
checkpoint Factor checkpoint so it can be used by helm-op too 1 year ago
cluster Include initContainers in images to fetch 1 year ago
cmd Put some trace logging into the cache refresh code 1 year ago
daemon Allow multiple config paths within a git repo 1 year ago
deploy Reduce memcache logging by default 1 year ago
deploy-helm Bump helm-op version in deploy-helm 1 year ago
docker Remove the helm prefix from helm-op version Fix #1320 1 year ago
errors Downgrade non-specific errors to application-level 1 year ago
event Omit changes that aren't, in auto-releases 1 year ago
git Reduce releaser test verbiage 1 year ago
guid Make new subscriptions kick old subscriptions 3 years ago
http Update UpStream to register as V10 1 year ago
image Change image cache expiry to adaptive scheme 1 year ago
integrations Purge release if install fails If a chart is broken, Tiller will reserve the name and mark the release as failed. If at a later time the chart is fixed, helm-op can't install it anymore because the release name is in use. Purging the release after each failed install allows helm-op to keep retrying the installation. 1 year ago
internal_docs Document the Helm chart release process 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 Remove spurious ServicesWithPolicies 1 year ago
registry Avoid timeouts by testing with a stable image repo 1 year ago
release Add a test for releasing initContainers 1 year ago
remote Remove spurious ServicesWithPolicies 1 year ago
resource Verify releases with a model comparison 1 year ago
site fix wrong link to from 1 year ago
ssh Generate keys in a separate tmpfs volume 1 year ago
sync Allow multiple config paths within a git repo 1 year ago
test Keep current-context 2 years ago
update Exclude locked workloads for container type release 1 year ago
.gitignore Basic integration tests 2 years ago add empty changelog entries for the upcoming release 1 year ago add empty changelog entries for the upcoming release 1 year ago Move code of conduct into its own file. 1 year ago add note about where to find GH issues as first-time contributor 1 year ago
DCO docs: steal and DCO docs from scope, modify slightly 1 year ago
Gopkg.lock Use dep v0.4.1 to generate Gopkg.lock 1 year ago
Gopkg.toml Update go-k8s-portforward to latest version to provide kubectl auth plugins for GKE, AWS, to support managed clusters. 1 year ago
LICENSE Initial commit 3 years ago
Makefile Build and upload Windows binary of fluxctl 1 year ago Move code of conduct into its own file. 1 year ago
flux.go Allow colons in the name component of resource IDs 1 year ago
lint Basic circle.yml, respecting Glide etc. 3 years ago
resourceid_test.go Allow colons in the name component of resource IDs 1 year 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 an 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:

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

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!