From 9e10d98d07f27b2f8e6e167c1e986d89b258e787 Mon Sep 17 00:00:00 2001 From: Jim Bugwadia Date: Wed, 23 Feb 2022 17:58:26 -0800 Subject: [PATCH] add options Signed-off-by: Jim Bugwadia --- .../setup/best-practices/enforcing-pod-security-standards.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/en/docs/setup/best-practices/enforcing-pod-security-standards.md b/content/en/docs/setup/best-practices/enforcing-pod-security-standards.md index 9ddb8b4108..59b19c01f5 100644 --- a/content/en/docs/setup/best-practices/enforcing-pod-security-standards.md +++ b/content/en/docs/setup/best-practices/enforcing-pod-security-standards.md @@ -70,6 +70,8 @@ few different ways: Other alternatives for enforcing security profiles are being developed in the Kubernetes ecosystem: +- [Kubewarden](https://github.com/kubewarden). +- [Kyverno](https://kyverno.io/policies/). - [OPA Gatekeeper](https://github.com/open-policy-agent/gatekeeper). The decision to go with a _built-in_ solution (e.g. PodSecurity admission controller) versus a