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.
Michael Bridgen bb576fadad
Merge pull request #2445 from wbiller/patch-1
2 days ago
.circleci Update CircleCI work dir to github.com/fluxcd 1 week ago
.github weaveworks -> fluxcd 1 month ago
api Change imports path from weaveworks to fluxcd 1 week ago
bin Upgrade `kubeyaml` to `0.7.0` 1 month ago
chart Update default value for helmOperator.createCRD 3 days ago
checkpoint Fixup arm and arm64 builds; Refactor Makefile; 4 months ago
cluster Change imports path from weaveworks to fluxcd 1 week ago
cmd Change imports path from weaveworks to fluxcd 1 week ago
daemon Change imports path from weaveworks to fluxcd 1 week ago
deploy Update version in chart, template, generated files 1 week ago
docker Upgrade `kubeyaml` to `0.7.0` 1 month ago
docs Remove `values.` prefix from annotation examples 1 week ago
errors Downgrade non-specific errors to application-level 1 year ago
event Change imports path from weaveworks to fluxcd 1 week ago
git Change imports path from weaveworks to fluxcd 1 week ago
gpg Change imports path from weaveworks to fluxcd 1 week ago
guid Make new subscriptions kick old subscriptions 2 years ago
http Change imports path from weaveworks to fluxcd 1 week ago
image Change org in image definition tests to 'fluxcd' 2 months ago
install Change imports path from weaveworks to fluxcd 1 week ago
integrations Change imports path from weaveworks to fluxcd 1 week ago
internal_docs Fixed broken URLs and mentions of old organization 1 month ago
job Change imports path from weaveworks to fluxcd 1 week ago
manifests Change imports path from weaveworks to fluxcd 1 week ago
metrics Standardize http metrics, to flux_request_duration 2 years ago
policy Change imports path from weaveworks to fluxcd 1 week ago
registry Change imports path from weaveworks to fluxcd 1 week ago
release Change imports path from weaveworks to fluxcd 1 week ago
remote Change imports path from weaveworks to fluxcd 1 week ago
resource Change imports path from weaveworks to fluxcd 1 week ago
snap Update snap/snapcraft.yaml 4 days ago
ssh Add the option to run fluxd outside a Kubernetes cluster 3 months ago
sync Change imports path from weaveworks to fluxcd 1 week ago
test Remove Helm operator bits from end to end tests 1 month ago
update Change imports path from weaveworks to fluxcd 1 week ago
.gitignore rename site/ to docs/ 1 month ago
.readthedocs.yml rename site/ to docs/ 1 month ago
CHANGELOG.md Update changelog for 1.14.2 1 week ago
CODE_OF_CONDUCT.md Move code of conduct into its own file. 11 months ago
CONTRIBUTING.md Restructure and split Flux and Helm op docs 1 month ago
DCO docs: steal CONTRIBUTING.md and DCO docs from scope, modify slightly 1 year ago
LICENSE Initial commit 3 years ago
MAINTAINERS Update Slack information in MAINTAINERS file 1 month ago
Makefile Change imports path from weaveworks to fluxcd 1 week ago
README.md Update README.md 1 week ago
go.mod Change imports path from weaveworks to fluxcd 1 week ago
go.sum Change imports path from weaveworks to fluxcd 1 week ago
tools.go Remove `k8s.io/code-generator` from go.mod 1 month ago

README.md

Flux

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!

History

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.

Integrations

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 mishi@linux.com.

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!