mirrors/kyverno
mirrors/kyverno
1
0
Fork 0
mirror of https://github.com/kyverno/kyverno.git synced 2025-03-20 23:02:36 +00:00
Code Activity

Update ADOPTERS.md (#12411)

Browse source 
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>
This commit is contained in:
CortNick 2025-03-14 11:05:24 +01:00 • committed by GitHub
parent ff7f57713e
commit a2ed5014e3
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 1 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
ADOPTERS.md
View file

@ -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. |
<!-- append the line below to the table
| [name](URL) | brief description of how you are using Kyverno |
-->