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 e9e6195849 Add ability to append [ci skip] to commit messages 2 years ago
.circleci Don't release helm-operator when doing a flux release 2 years ago
api Move API v9 into its own package 2 years ago
apis/helm.integrations.flux.weave.works Finishes implementation of syncing due to repo chart changes; helm version to 2.8. 2 years ago
bin Finishes implementation of syncing due to repo chart changes; helm version to 2.8. 2 years ago
cluster Support for single quotes in YAML image value 2 years ago
cmd Add ability to append [ci skip] to commit messages 2 years ago
daemon Add ability to append [ci skip] to commit messages 2 years ago
deploy Bump flux-deployment image to 1.2.4 2 years ago
docker Give container images labels 2 years ago
errors Downgrade non-specific errors to application-level 2 years ago
event Supply more structured info in sync errors 2 years ago
git Add ability to append [ci skip] to commit messages 2 years ago
guid Make new subscriptions kick old subscriptions 3 years ago
http Merge pull request #974 from weaveworks/refactor/version-api 2 years ago
image Include digest and image identifier in image.Info 2 years ago
integrations Fixes cloning of non-master branches 2 years ago
internal_docs Add PR step to release instructions 2 years ago
job Extricate the Event types from history package 2 years ago
metrics Standardize http metrics, to flux_request_duration 3 years ago
policy Reorders deleting and applying during cluster syncing by resource kind 2 years ago
registry Avoid spin in cache refresh loop To implement the loop as described in the comment above it, when the backlog is empty we need to block until the refresh tick fires (or a priority image comes in). By having a default case, it's possible to spin. 2 years ago
release Remove mutex and make Config private in Checkout 2 years ago
remote Move API v9 into its own package 2 years ago
resource Clean up references to platform 2 years ago
site Add ability to append [ci skip] to commit messages 2 years ago
ssh Prefix ssh keygen tmpdir with ..weave- 3 years ago
sync Add ability to append [ci skip] to commit messages 2 years ago
test Keep current-context 2 years ago
update ReleaseKindExecute should be a ReleaseKind 2 years ago
.gitignore Basic integration tests 2 years ago
CHANGELOG.md Update CHANGELOG.md for 1.2.4 release 2 years ago
Gopkg.lock Fix: Changes command used to detect latest commits under the repo charts path 2 years ago
Gopkg.toml Finishes implementation of syncing due to repo chart changes; helm version to 2.8. 2 years ago
LICENSE Initial commit 4 years ago
Makefile Give container images labels 2 years ago
README.md Rewrite some FAQ answers and mention Flux Classic 2 years ago
flux.go Detangle service token from top-level package 2 years ago
lint Basic circle.yml, respecting Glide etc. 4 years ago

README.md

Flux

We believe that environments should be entirely version controlled. This is an anti-fragile measure to ensure stability through visibility. If anything fails, you can simply reapply the current state of the repository.

Flux is a tool that automatically ensures that the state of a cluster matches what is specified in version control (along with a few extra features).

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

CircleCI GoDoc

Get started by browsing through the documentation below.

Introduction to Flux

FAQ

How it works

Installing Flux

Using Flux

Upgrading to Flux v1

Troubleshooting

Developer information

Build documentation

Release documentation

Contribution

Flux follows a typical PR workflow. All contributions should be made as PRs that satisfy the guidelines below.

Guidelines

  • All code must abide Go Code Review Comments
  • Names should abide What’s in a name
  • Code must build on both Linux and Darwin, via plain go build
  • Code should have appropriate test coverage, invoked via plain go test

In addition, several mechanical checks are enforced. See the lint script for details.

Getting Help

If you have any questions about Flux and continuous delivery:

Your feedback is always welcome!