From a49ed4a35ccbab8d0a36cd4d5cd9516ee275e541 Mon Sep 17 00:00:00 2001
From: Jiaqi Luo <6218999+jiaqiluo@users.noreply.github.com>
Date: Wed, 1 Mar 2023 15:09:31 -0700
Subject: [PATCH] add a note that Rancher does not clean up the builtin PSPs

---
 .../create-pod-security-policies.md                         | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/create-pod-security-policies.md b/docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/create-pod-security-policies.md
index c88a8725755..1185d89fd2a 100644
--- a/docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/create-pod-security-policies.md
+++ b/docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/create-pod-security-policies.md
@@ -40,6 +40,12 @@ This policy is a relaxed version of the `restricted-noroot` policy, with almost
 
 This policy is equivalent to running Kubernetes with the PSP controller disabled. It has no restrictions on what pods can be deployed into a cluster or project.
 
+:::note important
+
+When disabling PSPs, default PSPs are **not** automatically deleted from your cluster. You must manually delete them if they're no longer needed.
+
+:::
+
 ## Creating PSPs
 
 Using Rancher, you can create a Pod Security Policy using our GUI rather than creating a YAML file.