From a2e9ae3a82950cdfb6e88ae417665a8925ce1b24 Mon Sep 17 00:00:00 2001 From: MBishop17 Date: Fri, 3 Aug 2018 17:01:13 -0700 Subject: [PATCH] adding Nate's corrections --- .../v2.x/en/admin-settings/pod-security-policies/_index.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) 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 6efc905d10a..638672727e9 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 @@ -35,11 +35,11 @@ Rancher ships with two default Pod Security Policies (PSPs): the `restricted` an - `unrestricted` - This policy is based on the Kubernetes [example restricted policy](https://kubernetes.io/docs/concepts/policy/pod-security-policy/#example-policies). This policy: + This policy is based on the Kubernetes [example restricted policy](https://kubernetes.io/docs/concepts/policy/pod-security-policy/#example-policies). It significantly restricts what types of pods can be deployed to a cluster or project. This policy: - - Prevents pods from running as an unprivileged user or from root. + - Prevent pods from running as a privileged user and prevents escalation of privileges. - Validates that server-required security mechanisms are in place (such as restricting what volumes can be mounted to only the core volume types and preventing root supplemental groups from being added). - - Significantly restricts what types of pods can be deployed to a cluster or project. + ## Creating Pod Security Policies