-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal for Flagger to join Flux project and CNCF #34
Comments
+1 great idea |
Flagger is a great fit for the Flux project. I'm 💯 on board with this. |
As a maintainer, I am completely +1 🥇 |
+1 without any doubt |
+💯 |
This was referenced Dec 21, 2020
Note this issue followed the correct procedure for decision making on the project level, according to Flux governance https://github.com/fluxcd/community/blob/main/GOVERNANCE.md#decision-making |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The Flagger authors are requesting for Flagger to join the fluxcd org.
Flagger extends Flux functionality with progressive delivery strategies like Canary Releases, A/B Testing and Blue/Green and it was specifically designed for GitOps style delivery.
Since the inception of the GitOps Toolkit, it’s clear that fluxcd/ will become more of a family of GitOps related projects. The Flagger maintainers are looking forward to making use of the toolkit components and simplifying Flagger this way. Consolidating the code-bases and thinking in terms of a “Flux Family of Projects” and writing up the roadmap accordingly should benefit both communities as a whole.
Background information:
We would like to present at one of the next Flux meetings and state our intent in more detail. We are looking forward to your questions and a good debate.
The text was updated successfully, but these errors were encountered: