1
0
Fork 0
mirror of https://github.com/kyverno/kyverno.git synced 2025-03-31 03:45:17 +00:00

Add adopter li (#8584)

* fix excessive logs

Signed-off-by: Jim Bugwadia <jim@nirmata.com>

* add LinkedIn to the Kyverno adopters list

Signed-off-by: Jim Bugwadia <jim@nirmata.com>

---------

Signed-off-by: Jim Bugwadia <jim@nirmata.com>
This commit is contained in:
Jim Bugwadia 2023-10-04 21:05:19 -07:00 committed by GitHub
parent 4762e0807e
commit a5028b1f08
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -36,6 +36,8 @@ The list of organizations that have publicly shared the usage of Kyverno:
| [Hexagon](https://hexagon.com/) | 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. |
| [Grover Group GmbH](https://www.grover.com) | 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. |
| [IITS Consulting](https://iits-consulting.de/) | 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. |
| [LinkedIn](https://www.linkedin.com/) | Policy enforcement on our on-prem Kubernetes clusters. |
<!-- append the line below to the table
| [name](URL) | brief description of how you are using Kyverno |