From a2ed5014e350d61070992418574752a36df610e2 Mon Sep 17 00:00:00 2001 From: CortNick <104345443+CortNick@users.noreply.github.com> Date: Fri, 14 Mar 2025 11:05:24 +0100 Subject: [PATCH] Update ADOPTERS.md (#12411) X3M Ads has completed the Adopters form and this PR is to add the company and the use case that they shared with us to the official list of Kyverno OSS Adopters. Signed-off-by: CortNick <104345443+CortNick@users.noreply.github.com> --- ADOPTERS.md | 1 + 1 file changed, 1 insertion(+) diff --git a/ADOPTERS.md b/ADOPTERS.md index 0788a9766a..f6f61873c5 100644 --- a/ADOPTERS.md +++ b/ADOPTERS.md @@ -49,6 +49,7 @@ The list of organizations that have publicly shared the usage of Kyverno: | [Tigera](https://www.tigera.io/) | Kubernetes Policy and Governance | | [kubriX platform](kubrix.io) | Policy enforcement and automation of your kubrix platform using GitOps | | [OVHcloud](https://www.ovhcloud.com/) | At OVHcloud, we advise our customers to [deploy Kyverno as a policy engine on their Managed Kubernetes (MKS) clusters](https://help.ovhcloud.com/csm/en-gb-public-cloud-kubernetes-install-kyverno?id=kb_article_view&sysparm_article=KB0049839) and we also use it internally to enforce the security of several of our products. | +| [X3M Ads](https://x3mads.com/) | At X3M Ads, we primarily use Kyverno for mutating resources, such as changing pod images to our internal Harbor registry, managing topology distribution and adding node metadata to pods for improved observability. |