GitOps Tools¶

⚠️ This could be outdated! ⚠️

Last update: Mar 14, 2019

Weave Flux ¶

One Flux Controller per repo
- One repo could be scanned from multiple flux controllern
- It's possible to handle multiple envs in one repo (FAQ)
- Removing resources are still an experimental feature which has to be enabled manually
- Helm Charts will not be removed if the HelmRelease CRD is deleted from the repo. The HelmRelease CRD-Object has be removed manually in the cluster. (FAQ)
Can be extended via operators (e.g. Helm Operator)
- Is working with real Helm Releases
Use CRD for defining a HelmRelease
Docker Registry scanning for new Images
- Scanning via Regex (e.g. master-*, dev-*)
Namespace whitelisting is possible (FAQ)
Events could be thrown to slack and webhooks (GitHub Repo)
Flux Tag in Repository to mark the latest deployed commit
- NEGATIVE Needs write access on the repo
- No sync back from cluster to repo
Integrates with Weave Cloud
Flux Operator to easily install multiple Flux instances

Running as a k8s controller
Able to deploy to multiple clusters
Automated or manual syncing of applications to its desired state
Web UI which provides real-time view of application activity
CLI for automation and CI integration
Webhook integration
Prometheus metrics
SSO Integration
NEGATIVE deployes helm charts as normal k8s resources
- -> No helm rollback mechanism or other helm benefits
NEGATIVE deployment via helm chart possible but not very well documented