kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Fix typos in Markdown links. (#32802) 

* Fix typos in Markdown links.

* Test

Co-authored-by: Mads Jensen <atombrella@users.noreply.github.com>
pull/32811/head
Mads Jensen 2022-04-08 09:16:41 +02:00 committed by GitHub
parent d8dfd81d0c
commit eefc776e29
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/en/docs/reference/access-authn-authz/admission-controllers.md
View File

@ -782,7 +782,7 @@ This admission controller will deny any Pod that attempts to set certain escalat
fields, as shown in the
[Configure a Security Context for a Pod or Container](/docs/tasks/configure-pod-container/security-context/)
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,
then you could use this admission controller to restrict the set of values a security context can take.

2
content/en/docs/tasks/administer-cluster/securing-a-cluster.md
View File

@ -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
[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
be able to escape their containers and use this widened access to elevate their privileges.