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.
Hidde Beydals 10e6f73cbf
Make `fluxctl` respect the kube config context NS (#2255)
1 day ago
.circleci Push images to DockerHub fluxcd org 1 week ago
.github more Flux → Weave Flux 3 weeks ago
api Change org in image definition tests to 'fluxcd' 6 days ago
bin Update kubeyaml to '0.6.1' 2 weeks ago
chart Re-implement registry.ecr.require 1 day ago
checkpoint Fixup arm and arm64 builds; Refactor Makefile; 2 months ago
cluster Merge pull request #2201 from weaveworks/refac 6 days ago
cmd Make `fluxctl` respect the kube config context NS 1 day ago
daemon Merge pull request #2201 from weaveworks/refac 6 days ago
deploy Change org in image definitions to 'fluxcd' 6 days ago
deploy-helm Fixed rollback.timeout type definition in CRD 4 days ago
docker Update labels in Dockerfiles to match `fluxcd` org 6 days ago
errors Downgrade non-specific errors to application-level 1 year ago
event Merge pull request #2201 from weaveworks/refac 6 days ago
git Merge pull request #2201 from weaveworks/refac 6 days ago
gpg tests Flux → Weave Flux 3 weeks ago
guid Make new subscriptions kick old subscriptions 2 years ago
http Merge pull request #2201 from weaveworks/refac 6 days ago
image Change org in image definition tests to 'fluxcd' 6 days ago
integrations Merge remote-tracking branch 'origin/release/1.13.x' 6 days ago
internal_docs Update internal docs about release process 1 month ago
job Break dependencies among git, job, event packages 1 year ago
manifests Merge pull request #2201 from weaveworks/refac 6 days ago
metrics Standardize http metrics, to flux_request_duration 2 years ago
policy Merge pull request #2201 from weaveworks/refac 6 days ago
registry Run credentials tests in parallel 1 day ago
release Merge pull request #2201 from weaveworks/refac 6 days ago
remote Merge pull request #2201 from weaveworks/refac 6 days ago
resource Merge pull request #2201 from weaveworks/refac 6 days ago
site Use correct Helm repository domain in docs 1 day ago
snap more Flux → Weave Flux 3 weeks ago
ssh Add the option to run fluxd outside a Kubernetes cluster 1 month ago
sync Merge pull request #2201 from weaveworks/refac 6 days ago
test Merge pull request #2202 from weaveworks/kind-0.4 6 days ago
update Merge pull request #2201 from weaveworks/refac 6 days ago
.gitignore ignore .snap.xdelta3 files as well - they're generated when uploading to the snap store 1 month ago
CHANGELOG-helmop.md Add changelog entry for Helm operator v0.10.0 6 days ago
CHANGELOG.md Merge remote-tracking branch 'origin/release/1.13.x' 6 days ago
CODE_OF_CONDUCT.md Move code of conduct into its own file. 9 months ago
CONTRIBUTING.md clarify docs a little, add links 1 month ago
DCO docs: steal CONTRIBUTING.md and DCO docs from scope, modify slightly 10 months ago
LICENSE Initial commit 3 years ago
MAINTAINERS Update MAINTAINERS and include email addresses 2 months ago
Makefile Merge pull request #2207 from 2opremio/get-dependencies-faster 6 days ago
README.md Change badges to fluxcd 6 days ago
go.mod Restore github/justinbarrick/go-k8s-portforward 1 month ago
go.sum Restore github/justinbarrick/go-k8s-portforward 1 month ago
tools.go Fix `make check-generated` 1 month ago

README.md

Flux

Notice Flux is moving house! Please see https://github.com/weaveworks/flux/wiki/MoveToFluxCD

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.

Features

Its major features are:

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

Get started by browsing through the documentation below:

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.

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting a Flux project maintainer, or Alexis Richardson <alexis@weave.works>. 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!