fix runasgroup psp policy

kubernetes · May 1, 2019 · a49f970 · a49f970
1 parent b191b55
commit a49f970
Showing 1 changed file with 2 additions and 2 deletions.
diff --git 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.