From 8ecb2b404b4539768e5b7b17311680a39205ff05 Mon Sep 17 00:00:00 2001 From: Slava Semushin Date: Tue, 24 Oct 2017 18:28:20 +0200 Subject: [PATCH] pod-security-policy.md: add links to the page about admission plugins. --- docs/concepts/policy/pod-security-policy.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/concepts/policy/pod-security-policy.md b/docs/concepts/policy/pod-security-policy.md index a6748efba4..346556972a 100644 --- a/docs/concepts/policy/pod-security-policy.md +++ b/docs/concepts/policy/pod-security-policy.md @@ -143,8 +143,9 @@ its parent. ## Admission -_Admission control_ with `PodSecurityPolicy` allows for control over the -creation and modification of resources based on the capabilities allowed in the cluster. +[_Admission control_ with `PodSecurityPolicy`](/docs/admin/admission-controllers/#podsecuritypolicy) +allows for control over the creation and modification of resources based on the +capabilities allowed in the cluster. Admission uses the following approach to create the final security context for the pod: @@ -210,7 +211,7 @@ In order to use Pod Security Policies in your cluster you must ensure the following 1. You have enabled the API type `extensions/v1beta1/podsecuritypolicy` (only for versions prior 1.6) -1. You have enabled the admission controller `PodSecurityPolicy` +1. [You have enabled the admission control plug-in `PodSecurityPolicy`](/docs/admin/admission-controllers/#how-do-i-turn-on-an-admission-control-plug-in) 1. You have defined your policies ## Working With RBAC