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.
Get started by browsing through the documentation below.
Developer information
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:
- Invite yourself to the #weave-community slack channel.
- Ask a question on the #weave-community slack channel.
- Join the Weave User Group and get invited to online talks, hands-on training and meetups in your area.
- Send an email to weave-users@weave.works
- File an issue.
Your feedback is always welcome!