Skip to content

Commit b206417

Browse files
committed
Fix typo in relative URL
1 parent 4e15cff commit b206417

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/en/blog/_posts/2021-04-08-PodSecurityPolicy-Past-Present-and-Future.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ Until then, PSP is still PSP. There will be at least a year during which the new
2121

2222
## What is PodSecurityPolicy?
2323

24-
[PodSecurityPolicy](/docs/concepts/policy/pod-security-policy/) is a built-in [admission controller](o/blog/2019/03/21/a-guide-to-kubernetes-admission-controllers/) that allows a cluster administrator to control security-sensitive aspects of the Pod specification.
24+
[PodSecurityPolicy](/docs/concepts/policy/pod-security-policy/) is a built-in [admission controller](/blog/2019/03/21/a-guide-to-kubernetes-admission-controllers/) that allows a cluster administrator to control security-sensitive aspects of the Pod specification.
2525

2626
First, one or more PodSecurityPolicy resources are created in a cluster to define the requirements Pods must meet. Then, RBAC rules are created to control which PodSecurityPolicy applies to a given pod. If a pod meets the requirements of its PSP, it will be admitted to the cluster as usual. In some cases, PSP can also modify Pod fields, effectively creating new defaults for those fields. If a Pod does not meet the PSP requirements, it is rejected, and cannot run.
2727

0 commit comments

Comments
 (0)