From a49f97058d9f3c0309d1ecc149d41079304307ad Mon Sep 17 00:00:00 2001 From: Mayank Kumar Date: Wed, 1 May 2019 14:38:02 -0700 Subject: [PATCH] fix runasgroup psp policy --- content/en/docs/concepts/policy/pod-security-policy.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/concepts/policy/pod-security-policy.md b/content/en/docs/concepts/policy/pod-security-policy.md index 977a1b6a19c77..c34983cccdf49 100644 --- a/content/en/docs/concepts/policy/pod-security-policy.md +++ b/content/en/docs/concepts/policy/pod-security-policy.md @@ -493,8 +493,8 @@ recommended with this strategy. - *MustRunAs* - Requires at least one `range` to be specified. Uses the minimum value of the first range as the default. Validates against all ranges. -- *MustRunAsNonRoot* - Requires that the pod be submitted with a non-zero -`runAsUser` or have the `USER` directive defined (using a numeric GID) in the +- *MayRunAs* - Does not Require that RunAsGroup be specified. However, when RunAsGroup are +specified, they have to fall in the defined range. image. No default provided. Setting `allowPrivilegeEscalation=false` is strongly recommended with this strategy. - *RunAsAny* - No default provided. Allows any `runAsGroup` to be specified.