docs/concepts/policy/pod-security-policy.md: improve AllowPrivilegeEscalation description. (#8000)
This commit is contained in:
committed by
k8s-ci-robot
parent
8dff71a36b
commit
5b29154c0e
@@ -480,14 +480,10 @@ from changing the effective user ID, and prevent files from enabling extra
|
||||
capabilities (e.g. it will prevent the use of the `ping` tool). This behavior is
|
||||
required to effectively enforce `MustRunAsNonRoot`.
|
||||
|
||||
It defaults to `nil`. The default behavior of `nil` allows privilege escalation
|
||||
so as to not break setuid binaries. Setting it to `false` ensures that no child
|
||||
process of a container can gain more privileges than its parent.
|
||||
|
||||
**AllowPrivilegeEscalation** - Gates whether or not a user is allowed to set the
|
||||
security context of a container to `allowPrivilegeEscalation=true`. This
|
||||
defaults to allowed. When set to false, the container's
|
||||
`allowPrivilegeEscalation` is defaulted to false.
|
||||
defaults to allowed so as to not break setuid binaries. Setting it to `false`
|
||||
ensures that no child process of a container can gain more privileges than its parent.
|
||||
|
||||
**DefaultAllowPrivilegeEscalation** - Sets the default for the
|
||||
`allowPrivilegeEscalation` option. The default behavior without this is to allow
|
||||
|
||||
Reference in New Issue
Block a user