From 0be7beae94c68b4b752afbec8ec7e6728b86975c Mon Sep 17 00:00:00 2001 From: William Jimenez Date: Wed, 4 Dec 2019 09:55:15 -0800 Subject: [PATCH] note requirements for using PSPs in a project --- .../v2.x/en/admin-settings/pod-security-policies/_index.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/rancher/v2.x/en/admin-settings/pod-security-policies/_index.md b/content/rancher/v2.x/en/admin-settings/pod-security-policies/_index.md index 51b190231ef..470f20bc51f 100644 --- a/content/rancher/v2.x/en/admin-settings/pod-security-policies/_index.md +++ b/content/rancher/v2.x/en/admin-settings/pod-security-policies/_index.md @@ -17,6 +17,8 @@ _Pod Security Policies_ (or PSPs) are objects that control security-sensitive as - You can override the default PSP by assigning a different PSP directly to the project. - Any workloads that are already running in a cluster or project before a PSP is assigned will not be checked if it complies with the PSP. Workloads would need to be cloned or upgraded to see if they pass the PSP. +>**NOTE:** You must enable PSPs at the cluster level before you can assign them to a project. This can be found under the "Edit cluster" menu. + Read more about Pod Security Policies in the [Kubernetes Documentation](https://kubernetes.io/docs/concepts/policy/pod-security-policy/). >**Best Practice:** Set pod security at the cluster level.