Skip to content
The GitOps Kubernetes operator
Branch: master
Clone or download
hiddeco Make `fluxctl` respect the kube config context NS (#2255)
Make `fluxctl` respect the kube config context NS
Latest commit 10e6f73 Jul 15, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.circleci Merge pull request #2195 from 2opremio/bump-circleci-image Jul 10, 2019
.github more Flux → Weave Flux Jun 25, 2019
api Change org in image definition tests to 'fluxcd' Jul 10, 2019
bin Update kubeyaml to '0.6.1' Jul 2, 2019
chart Re-implement registry.ecr.require Jul 15, 2019
checkpoint Fixup arm and arm64 builds; Refactor Makefile; Apr 19, 2019
cluster Support more oddball image ref compositions Jul 2, 2019
cmd Make `fluxctl` respect the kube config context NS Jul 15, 2019
daemon Only require image TS when it is used for sorting Jul 1, 2019
deploy-helm Fixed rollback.timeout type definition in CRD Jul 12, 2019
deploy Change org in image definitions to 'fluxcd' Jul 10, 2019
docker Update labels in Dockerfiles to match `fluxcd` org Jul 10, 2019
errors Downgrade non-specific errors to application-level Feb 15, 2018
event Merge pull request #2201 from weaveworks/refac Jul 10, 2019
git Allow Google Cloud SDK env entries for git Jul 8, 2019
gpg tests Flux → Weave Flux Jun 25, 2019
guid Make new subscriptions kick old subscriptions Dec 14, 2016
http Move Upstream methods into public API Jul 2, 2019
image Change org in image definition tests to 'fluxcd' Jul 10, 2019
integrations Merge remote-tracking branch 'origin/release/1.13.x' Jul 10, 2019
internal_docs Update internal docs about release process Jun 13, 2019
job Break dependencies among git, job, event packages Apr 3, 2018
manifests Merge pull request #2201 from weaveworks/refac Jul 10, 2019
metrics Standardize http metrics, to flux_request_duration Feb 2, 2017
policy Merge pull request #2201 from weaveworks/refac Jul 10, 2019
registry Run credentials tests in parallel Jul 15, 2019
release Merge pull request #2201 from weaveworks/refac Jul 10, 2019
remote Move Upstream methods into public API Jul 2, 2019
resource Merge pull request #2201 from weaveworks/refac Jul 10, 2019
site Use correct Helm repository domain in docs Jul 15, 2019
snap more Flux → Weave Flux Jun 25, 2019
ssh Add the option to run fluxd outside a Kubernetes cluster Jun 10, 2019
sync Merge pull request #2201 from weaveworks/refac Jul 10, 2019
test Merge pull request #2202 from weaveworks/kind-0.4 Jul 10, 2019
update Merge pull request #2201 from weaveworks/refac Jul 10, 2019
.gitignore ignore .snap.xdelta3 files as well - they're generated when uploading… Jun 3, 2019
CHANGELOG-helmop.md Add changelog entry for Helm operator v0.10.0 Jul 10, 2019
CHANGELOG.md Merge remote-tracking branch 'origin/release/1.13.x' Jul 10, 2019
CODE_OF_CONDUCT.md Move code of conduct into its own file. Sep 21, 2018
CONTRIBUTING.md clarify docs a little, add links May 29, 2019
DCO docs: steal CONTRIBUTING.md and DCO docs from scope, modify slightly Aug 28, 2018
LICENSE Initial commit Jul 7, 2016
MAINTAINERS Update MAINTAINERS and include email addresses Apr 30, 2019
Makefile Merge pull request #2207 from 2opremio/get-dependencies-faster Jul 10, 2019
README.md Change badges to fluxcd Jul 10, 2019
go.mod Restore github/justinbarrick/go-k8s-portforward Jun 6, 2019
go.sum Restore github/justinbarrick/go-k8s-portforward Jun 6, 2019
tools.go Fix `make check-generated` May 23, 2019

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!

You can’t perform that action at this time.