42607aadc3
This change adds support for running `suspend/resume` on multiple supported resources at the same time. This improves the user experience by converting ``` flux suspend ks operator && \ flux suspend ks database && \ flux suspend ks app ``` to ``` flux suspend ks operator database app ``` This works for all types of resources (Kustomizations, Sources, etc.) since it has been implemented at the `suspend.go` and `resume.go` level. When the `--wait` flag is passed to the `resume` command, then Flux will wait for all resources in parallel within a goroutine each. Each object is only processed once, even if user provided its name more than once. If suspension or resuming fails for one object, it is still carried out for the remaining objects. As a special case, the old behaviour of `resume` is retained, i.e. when only one object name is provided, `resume` waits for the object to become ready even if the `--wait` flag is not provided. In all other cases the `--wait` flag is always considered. closes #3746 closes #3793 Co-Authored-By: Max Jonas Werner <mail@makk.es> Signed-off-by: Rishikesh Nair <alienware505@gmail.com> Signed-off-by: Max Jonas Werner <mail@makk.es> |
2 years ago | |
|---|---|---|
| .github | 2 years ago | |
| action | 2 years ago | |
| cmd/flux | 2 years ago | |
| docs | 2 years ago | |
| install | 2 years ago | |
| internal | 2 years ago | |
| manifests | 2 years ago | |
| pkg | 2 years ago | |
| rfcs | 2 years ago | |
| tests | 2 years ago | |
| .gitignore | 3 years ago | |
| .goreleaser.yml | 2 years ago | |
| CODE_OF_CONDUCT.md | 5 years ago | |
| CONTRIBUTING.md | 2 years ago | |
| DCO | 5 years ago | |
| Dockerfile | 2 years ago | |
| LICENSE | 5 years ago | |
| MAINTAINERS | 3 years ago | |
| Makefile | 2 years ago | |
| README.md | 2 years ago | |
| go.mod | 2 years ago | |
| go.sum | 2 years ago | |
| netlify.toml | 4 years ago | |
README.md
Flux version 2
Flux is a tool for keeping Kubernetes clusters in sync with sources of configuration (like Git repositories and OCI artifacts), and automating updates to configuration when there is new code to deploy.
Flux version 2 ("v2") is built from the ground up to use Kubernetes' API extension system, and to integrate with Prometheus and other core components of the Kubernetes ecosystem. In version 2, Flux supports multi-tenancy and support for syncing an arbitrary number of Git repositories, among other long-requested features.
Flux v2 is constructed with the GitOps Toolkit, a set of composable APIs and specialized tools for building Continuous Delivery on top of Kubernetes.
Flux is a Cloud Native Computing Foundation (CNCF) project, used in production by various organisations and cloud providers.
Quickstart and documentation
To get started check out this guide on how to bootstrap Flux on Kubernetes and deploy a sample application in a GitOps manner.
For more comprehensive documentation, see the following guides:
- Ways of structuring your repositories
- Manage Helm Releases
- Automate image updates to Git
- Manage Kubernetes secrets with Mozilla SOPS
If you need help, please refer to our Support page.
GitOps Toolkit
The GitOps Toolkit is the set of APIs and controllers that make up the runtime for Flux v2. The APIs comprise Kubernetes custom resources, which can be created and updated by a cluster user, or by other automation tooling.
You can use the toolkit to extend Flux, or to build your own systems for continuous delivery -- see the developer guides.
Components
- Source Controller
- Kustomize Controller
- Helm Controller
- Notification Controller
- Image Automation Controllers
Community
Need help or want to contribute? Please see the links below. The Flux project is always looking for new contributors and there are a multitude of ways to get involved.
- Getting Started?
- Look at our Get Started guide and give us feedback
- Need help?
- First: Ask questions on our GH Discussions page.
- Second: Talk to us in the #flux channel on CNCF Slack.
- Please follow our Support Guidelines (in short: be nice, be respectful of volunteers' time, understand that maintainers and contributors cannot respond to all DMs, and keep discussions in the public #flux channel as much as possible).
- Have feature proposals or want to contribute?
- Propose features on our GitHub Discussions page.
- Join our upcoming dev meetings (meeting access and agenda).
- Join the flux-dev mailing list.
- Check out how to contribute to the project.
- Check out the project roadmap.
Events
Check out our events calendar, both with upcoming talks, events and meetings you can attend. Or view the resources section with past events videos you can watch.
We look forward to seeing you with us!