Proposal for Flagger to join Flux project and CNCF

[stefanprodan]

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:

• Approval of Flagger maintainers (Stefan Prodan and Takeshi Yoneda)
• Approval from Weaveworks to transfer Flagger and its copyright to fluxcd org (and thus, CNCF)
• Upcoming roadmap for Flagger includes GitOps Toolkit integration
• License, dependencies and copyright review can be found here

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.

[monadic]

+1 great idea

[squaremo]

Flagger is a great fit for the Flux project. I'm 💯 on board with this.

[mathetake]

As a maintainer, I am completely +1 🥇

[hiddeco]

+1 without any doubt

[scottrigby]

+💯

[scottrigby]

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