From e3885d04abfb0e56476594dc47429edd56f176c9 Mon Sep 17 00:00:00 2001 From: caiconkhicon Date: Fri, 28 Feb 2020 11:01:30 +0100 Subject: [PATCH] Fix wrong apiVersion for PodSecurityPolicy To create a PodSecurityPolicy, the apiVersion `policy/v1beta1` should be used. If I apply the current manifest, which use `apiVersion: policy/v1beta1`, it throws out the error: "no matches for kind "PodSecurityPolicy" in version "extensions/v1beta1" --- content/rancher/v2.x/en/security/hardening-2.3.3/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rancher/v2.x/en/security/hardening-2.3.3/_index.md b/content/rancher/v2.x/en/security/hardening-2.3.3/_index.md index 00eb91129ef..488c6fbcc4d 100644 --- a/content/rancher/v2.x/en/security/hardening-2.3.3/_index.md +++ b/content/rancher/v2.x/en/security/hardening-2.3.3/_index.md @@ -613,7 +613,7 @@ addons: | kind: Group name: system:authenticated --- - apiVersion: extensions/v1beta1 + apiVersion: policy/v1beta1 kind: PodSecurityPolicy metadata: name: restricted-psp