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.
Sam Broughton 49be450e3a Replace docker.io with index.docker.io in ImageID 3 years ago
api Move instance DB and instance config into service/ 3 years ago
bin Creating a new release will prompt circle to upload binaries to release. 3 years ago
cluster Add missing label to Logger.Log invocation 3 years ago
cmd Deprecate --docker-config argument rather than removing 3 years ago
daemon Merge pull request #694 from weaveworks/dont-run-auto-nops 3 years ago
db Rename db migation conflict 3 years ago
deploy Give the example deployment a released image version 3 years ago
docker Make test for tag safer 3 years ago
git Merge pull request #667 from weaveworks/better-sync-notification 3 years ago
guid Make new subscriptions kick old subscriptions 3 years ago
history Correct an off-by-one introduced by typo 3 years ago
http Merge pull request #656 from weaveworks/more-graceful-restarts 3 years ago
integrations/github Move http/error folder so the package name matches the import 3 years ago
internal_docs Correct suggested format of tag 3 years ago
job Change the job queue contract 3 years ago
metrics Standardize http metrics, to flux_request_duration 3 years ago
notifications Elide sync notification when reported as release 3 years ago
policy Address review comments 3 years ago
registry Parse docker credentials from imagePullRequests (not .dockerconfig) (#678) 3 years ago
release Move policy filtering logic from Manifests to policy package 3 years ago
remote Remove `flux status` command from help. Slight rewording. 3 years ago
resource Make "ignore" a first-class policy 3 years ago
server Expand notifications to "sync" events 3 years ago
service Expand notifications to "sync" events 3 years ago
site Parse docker credentials from imagePullRequests (not .dockerconfig) (#678) 3 years ago
ssh Prefix ssh keygen tmpdir with ..weave- 3 years ago
sync Remove unused constants 3 years ago
update Log failure instead of returning on CollectAvailableImages 3 years ago
vendor Revert "Use official version of heroku registry client." 3 years ago
.gitignore Refactor of cache 3 years ago
CHANGELOG.md Be specific about how 'newer' Kubernetes 3 years ago
LICENSE Initial commit 4 years ago
Makefile Use Darwinic means to get a kernel version 3 years ago
README.md Add a CI badge and pare down some verbiage 3 years ago
circle.yml Include pre-releases in tags that trigger an upload 3 years ago
errors.go Avoid using 500s for application-level errors from the daemon 3 years ago
errors_test.go Expose helpful errors from releases as well 3 years ago
flux.go Add service policies to ListServices result 3 years ago
image.go Replace docker.io with index.docker.io in ImageID 3 years ago
image_test.go Parse docker credentials from imagePullRequests (not .dockerconfig) (#678) 3 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

Flux Example

Get started by browsing through the documentation below.

Introduction to Flux

How it works

Installing Flux

Using Flux

FAQ

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!