Proposal: Kyverno to Graduation

[realshuting]

Hello TOC and CNCF community 👋

We are proposing Kyverno to become a CNCF Graduated project

What is Kyverno?

Kyverno is a Kubernetes policy engine that was created to validate, mutate, generate, and cleanup Kubernetes resources, including custom resources. Kyverno also offers built-in image verification rules to help secure the software supply chain by verifying signatures and attestations in either Sigstore Cosign and CNCF Notation formats.

Why are we ready to graduate?

Kyverno graduated to Incubating status in July 2022 and has seen steady growth of its community. The GitHub stars for Kyverno itself has experienced an impressive growth from 2537 to 4700, and there are 2,500+ members registered for the Kyverno community Slack. The Kyverno organization has 1452 contributors from 280+ companies. Kyverno is used in production and at scale by several end-user organizations like Deutsche Telekom, Spotify, The US Department of Defense, LinkedIn, Vodafone, and Yahoo.

Kyverno completed a fuzzing security audit and a third-party security review in November 2023.

The project maintainers believe that Kyverno meets the requirements for Graduation.

How you can help today

If you love Kyverno, please show your support with a 👍, ❤️ , or 🎉 on this PR! If you have adopted Kyverno, please add your story to Adopter.md.

[KRRK2015]

This is long overdue.... Go Kyverno....

[jimmyraywv]

This is a good idea! Kyverno is ready!

[Saim-Safdar]

Long overdue, best of luck, step in the right direction.

[rohitg00]

All the best.

[anusha94]

Go Kyverno 🚀

[patelrit]

This is awesome!

[eddycharly]

+ :100: !

[melshakir]

Yay - this is awesome!!

[rachnasud]

Way to go Kyverno.

[Namanl2001]

onwards and upwards 🚀

[CIPHERTron]

+1 Go Kyverno 🚀

[Sanskarzz]

kubectl kyverno apply graduationpolicy.yaml

[anubhav888]

+1 Go Kyverno!

[cdavisafc]

+1 YES!

[vponoikoait]

+1, great tool!

[dzolotusky]

hi @realshuting - @angellk and I will sponsor Kyverno's application to Graduation.

The next step for us is to schedule a kick off meeting as described in https://github.com/cncf/toc/blob/main/process/README.md#application-kick-off-meeting-is-scheduled-and-held. We'll need to go through the new process as outlined in that README file.

[angellk]

The TOC has requested a review be performed by TAG Contributor Strategy to ascertain the sustainability and direction of the project based on its documented and practiced governance. cc: @dzolotusky

[JimBugwadia]

The TOC has requested a review be performed by TAG Contributor Strategy to ascertain the sustainability and direction of the project based on its documented and practiced governance. cc: @dzolotusky

Requested at: https://github.com/cncf/tag-contributor-strategy/issues/696

[angellk]

Adopter interview 3/6 completed cc: @dzolotusky

[angellk]

Adopter interview 4/6 completed, cc: @dzolotusky

[dzolotusky]

The TOC and TAG CS have determined that the project does not meet the requirement to graduate due to all current maintainers being from a single company. After discussion with the project team, they are dedicated to improving maintainer diversity and will work towards meeting the criteria. When they do so, they will reapply, and the TOC will pick up the graduation where it left off.

[JimBugwadia]

@dzolotusky @angellk - thank you for your work on this! The transitions were unexpected, but we are making good progress in on-boarding new maintainers, which we believe will lead to a stronger community. We will re-visit, as soon as the process is back in eligibility status.