From 3dc86945ed0eac9af2cbf382989639cbea095540 Mon Sep 17 00:00:00 2001 From: Tyler Auerbeck Date: Wed, 25 Aug 2021 00:57:35 -0400 Subject: [PATCH] Fix link in pod-security-admission --- content/en/docs/concepts/security/pod-security-admission.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/security/pod-security-admission.md b/content/en/docs/concepts/security/pod-security-admission.md index 8df9d5616a..a1c87767c9 100644 --- a/content/en/docs/concepts/security/pod-security-admission.md +++ b/content/en/docs/concepts/security/pod-security-admission.md @@ -103,7 +103,7 @@ applied to workload resources, only to the resulting pod objects. You can define _exemptions_ from pod security enforcement in order allow the creation of pods that would have otherwise been prohibited due to the policy associated with a given namespace. Exemptions can be statically configured in the -[Admission Controller configuration](#configuring-the-admission-controller). +[Admission Controller configuration](/docs/tasks/configure-pod-container/enforce-standards-admission-controller/#configure-the-admission-controller). Exemptions must be explicitly enumerated. Requests meeting exemption criteria are _ignored_ by the Admission Controller (all `enforce`, `audit` and `warn` behaviors are skipped). Exemption dimensions include: