Skip to content
Kyverno

Community & Adoption

This page consolidates publicly available evidence of Kyverno production adoption, user feedback, and ecosystem recognition. It is maintained to satisfy the CNCF TOC requirement for linkable user-research and adoption data (ref issue #15473).

Production Adopters

Section titled “Production Adopters”

Kyverno is used in production by organizations across finance, telecommunications, government, cloud providers, and e-commerce. The full list of organizations that have publicly shared their usage is maintained in ADOPTERS.md in the project repository.

Notable adopters include:

  • Spotify — Uses Kyverno extensively for admission controller capabilities, including best practices and environment-specific data. Spotify received the CNCF Top End User Award 2023 in part for this work.
  • US DoD Platform One — The US Department of Defense Platform One uses Kyverno as its default policy engine for Kubernetes.
  • Deutsche Telekom — Uses Kyverno to enforce policies on managed clusters to prevent privilege escalation and enforce security rules.
  • Bloomberg — Uses Kyverno to replace custom validation and mutation webhooks in their internal Kubernetes-based platforms.
  • Vodafone — Policy enforcement and automation on an internal Kubernetes service offering.
  • LinkedIn — Policy enforcement on on-prem Kubernetes clusters.

Adopter Case Studies and Blog Posts

Section titled “Adopter Case Studies and Blog Posts”

The following posts on the Kyverno blog document real-world usage patterns and adopter experiences:

CNCF Annual Survey Data

Section titled “CNCF Annual Survey Data”

Kyverno is included in the CNCF Annual Survey as part of the policy management / security tooling category. The following survey reports are publicly available:

Community Feedback Channels

Section titled “Community Feedback Channels”

User feedback is collected through the following public channels:

Formal UX research studies and structured adopter interviews have not yet been conducted. This is a recognized gap and is tracked in issue #15473.