Merge pull request #2762 from GlorifiedTypist/feature/helm-chart-sops-support
Helm chart sops support
|1 day ago|
|.circleci||3 days ago|
|.github||2 days ago|
|bin||5 months ago|
|chart||1 day ago|
|cmd||2 days ago|
|deploy||6 days ago|
|docker||3 days ago|
|docs||3 days ago|
|integrations||1 week ago|
|internal||6 days ago|
|pkg||3 days ago|
|snap||1 month ago|
|test/e2e||2 days ago|
|.gitignore||2 months ago|
|.readthedocs.yml||5 months ago|
|CHANGELOG.md||6 days ago|
|CODE_OF_CONDUCT.md||1 year ago|
|CONTRIBUTING.md||4 months ago|
|DCO||1 year ago|
|LICENSE||3 years ago|
|MAINTAINERS||5 months ago|
|Makefile||3 days ago|
|README.md||4 days ago|
|go.mod||1 week ago|
|go.sum||1 week ago|
|tools.go||5 months ago|
Announcement Flux has joined CNCF as a sandbox project
We believe in GitOps:
kubectl, all changes go through git. Use diff tools to detect divergence between observed and desired state and get notifications.
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.
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.
| | | | | -- | --- | --- | |ABA English |APPUiO|Apester |ArangoDB Oasis|Avisi|B3i |Babylon Health|bimspot|Canva |CLVR Cloud Ltd|College of William & Mary|Control Plane |Crowd Riff|Cybrary|FireHydrant |Gini|HMCTS|IBM Cloudant |Improwised Technologies|Infabode|iQmetrix |karriere tutor GmbH|Limejump|loveholidays |LUNAR|Mettle|Mintel |Omise|Payout|Qordoba |Rakuten|Replicated|Rungway |Sage AI Labs|Starbucks|Troii |UK Hydrographic Office|Under Armour|VSHN |Walmart Chile|Weave Cloud|Workable |Working Group Two|Yusofleet|Yad2 |Zaaksysteem |||
If you too are using Flux in production; please submit a PR to add your organization to the list!
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.
With the following tutorials:
or just browse through the documentation.
Do you want to release your Helm charts in a declarative way?
Take a look at the
As Flux is Open Source, integrations are very straight-forward. Here are a few popular ones you might want to check out:
We welcome all kinds of contributions to Flux, be it code, issues you found, documentation, external tools, help and support or anything else really.
The Flux project adheres to the CNCF Code of Conduct.
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting a Flux project maintainer, or the CNCF mediator, Mishi Choudhary email@example.com.
To familiarise yourself with the project and how things work, you might be interested in the following:
If you have any questions about Flux and continuous delivery:
Your feedback is always welcome!