Project: Kyverno (Provisioning / Security & Compliance)
File: ADOPTERS.md

This is the list of organizations and users that have publicly shared how they are using Kyverno. Add your organization by creating a PR or Note: There are several other organizations and users that are unable to publicly share their stories but are active in the Kyverno community. We appreciate all our users and their contributions to making Kyverno a successful CNCF project. The list of organizations that have publicly shared the usage of Kyverno: | Organization | Success Story | |:--|:--| | | Policies for security and best practices | | | Kubeflow policies | | | Manage multi-tenancy and tenant isolation with GitOps | | | Kubernetes Policy and Governance | | | Support Kubernetes multi-user workflows through | | | Use Kyverno for mutation, to replace hand-written Webhooks, and generation to project common Kubernetes objects into many similar namespaces. | | | Use Kyverno for policy enforcement in all clusters, as well as part of our onboarding systems, populating new namespaces with requisite resources and secrets. | | | Use Kyverno extensively to handle defaulting logic on resources (primarily cluster-api resources) and some scenarios to replace PSPs to enforce certain restrictions. | | | Policy enforcement and automation on an internal k8s service offering. | | | Use Kyverno to enforce Policies on managed clusters to prevent right escalation of internal customers and to enforce security rules. | | | OpenShift Multi-Tenancy Self-Service for , managed with . Kyverno policies are available on . | | | Use Kyverno for replacing custom validation and mutation webhooks in their internal Kubernetes based platforms | | | Use Kyverno to enforce security policies rules, Kubernetes best practices for their internal container based workload on Kubernetes | | | In adoption planning to roll out to hundreds of production clusters using GitOps | | | Platform supports centralized deployment of Kyverno across clusters | | | Policy enforcement on managed clusters. Replacement of some in-house mutating webhooks. | | | Use Kyverno for mutation, to replace image tags to digest and also for validation for checking freshness of images. | | | | | | Learn more about Red Hat Advanced Cluster Management for Kubernetes for

| | Kyvernos policy enforcement is used to enforce the company's security guidelines. This is done using validation, mutation and generation techniques. | | | We use Kyverno to enforce security and best practises. | | | We successfully use Kyverno in our clusters for security, best practice enforcement, resource mutation, secret copying and more! | | | Policy enforcement and enabling selfservice for DevOps teams. | | | We leverage Kyverno to robustly enforce security policies. Additionally, as a Kubernetes swiss-knife, Kyverno fills our gap in our GitOps workflow by allowing us to apply complex configurations and customizations which are beyond the native capabilities of Kubernetes operators. | | | We have been using Kyverno to streamline our K8s security standards and also follow industry best practices for running workloads in K8s using policy enforcements. | | | Security is a piece of cake with Kyverno. Kyverno helped us to implement proper security for different kind of clients (medical/telecommunication/trading...). It solves problems like security enforcement, container image verification, distribution of imagePullSecrets and many more. | | | Policy enforcement on our on-prem Kubernetes clusters. | | | We have implemented Kyverno as a part of Auto compliance. We put policies to satisfy CIS Compliance for GKE as well as block anomalies detected by the Red Team. | | | Spotify uses Kyverno extensively for its admission controller capabilities, including best practices and environment-specific data. | | | The US Department of Defense (DoD) Platform One uses Kyverno as its default policy engine for Kubernetes. | | | We use Kyverno in almost all possible areas of security and automation, we call Kyverno as a "Multi-tenancy engine" since we host a multi-tenancy environment for our partners and customers. We have deprecated our own tooling that was complicated and hard to maintain, Thanks to Kyverno. | | | Use Kyverno to enforce security hardening and best practices, and mutate pod specs related to graceful shutdown handling, such as tGPS<sup>terminationGracePeriodSeconds</sup> and custom preStop script. | | | We are using Kyverno mutation policies in our pre-production environment to add default NetworkPolicy and to add labels to OKD resources. | <!-- append the line below to the table | | brief description of how you are using Kyverno | -->