From b20641723c9ce705d7fd3b9712fbffa7845f94f8 Mon Sep 17 00:00:00 2001 From: Tabitha Sable Date: Fri, 2 Apr 2021 23:11:31 -0500 Subject: [PATCH] Fix typo in relative URL --- .../2021-04-08-PodSecurityPolicy-Past-Present-and-Future.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/blog/_posts/2021-04-08-PodSecurityPolicy-Past-Present-and-Future.md b/content/en/blog/_posts/2021-04-08-PodSecurityPolicy-Past-Present-and-Future.md index c006be5538..68cec29e89 100644 --- a/content/en/blog/_posts/2021-04-08-PodSecurityPolicy-Past-Present-and-Future.md +++ b/content/en/blog/_posts/2021-04-08-PodSecurityPolicy-Past-Present-and-Future.md @@ -21,7 +21,7 @@ Until then, PSP is still PSP. There will be at least a year during which the new ## What is PodSecurityPolicy? -[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. +[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. 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.