Fix typos in Markdown links. (#32802)
* Fix typos in Markdown links. * Test Co-authored-by: Mads Jensen <atombrella@users.noreply.github.com>
This commit is contained in:
parent
d8dfd81d0c
commit
eefc776e29
|
|
@ -782,7 +782,7 @@ This admission controller will deny any Pod that attempts to set certain escalat
|
||||||
fields, as shown in the
|
fields, as shown in the
|
||||||
[Configure a Security Context for a Pod or Container](/docs/tasks/configure-pod-container/security-context/)
|
[Configure a Security Context for a Pod or Container](/docs/tasks/configure-pod-container/security-context/)
|
||||||
task.
|
task.
|
||||||
If you don't use [Pod Security admission]((/docs/concepts/security/pod-security-admission/),
|
If you don't use [Pod Security admission](/docs/concepts/security/pod-security-admission/),
|
||||||
[PodSecurityPolicies](/docs/concepts/security/pod-security-policy/), nor any external enforcement mechanism,
|
[PodSecurityPolicies](/docs/concepts/security/pod-security-policy/), nor any external enforcement mechanism,
|
||||||
then you could use this admission controller to restrict the set of values a security context can take.
|
then you could use this admission controller to restrict the set of values a security context can take.
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -243,7 +243,7 @@ like the `kube-system` namespace, because those pods can gain access to service
|
||||||
or run with elevated permissions if those service accounts are granted access to permissive
|
or run with elevated permissions if those service accounts are granted access to permissive
|
||||||
[PodSecurityPolicies](/docs/concepts/security/pod-security-policy/).
|
[PodSecurityPolicies](/docs/concepts/security/pod-security-policy/).
|
||||||
|
|
||||||
If you use [Pod Security admission]((/docs/concepts/security/pod-security-admission/) and allow
|
If you use [Pod Security admission](/docs/concepts/security/pod-security-admission/) and allow
|
||||||
any component to create Pods within a namespace that permits privileged Pods, those Pods may
|
any component to create Pods within a namespace that permits privileged Pods, those Pods may
|
||||||
be able to escape their containers and use this widened access to elevate their privileges.
|
be able to escape their containers and use this widened access to elevate their privileges.
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue