From 5f5934aee43889371d5d82db595d4236cc92eb59 Mon Sep 17 00:00:00 2001 From: Mauren Berti <698465+stormqueen1990@users.noreply.github.com> Date: Wed, 19 Apr 2023 11:49:54 -0400 Subject: [PATCH 1/4] Add admonition for caveat on finding PSPs in use Add a caution admonition for a caveat on using the kubectl get psp strategy to find which PSPs are still in use in the cluster. --- .../pod-security-standards.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/pod-security-standards.md b/docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/pod-security-standards.md index e5b7448761a..7e74443f907 100644 --- a/docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/pod-security-standards.md +++ b/docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/pod-security-standards.md @@ -24,6 +24,10 @@ You must perform the following steps _while still in Kubernetes v1.24_: 1. Map your active PSPs to Pod Security Standards: 1. See which PSPs are still active in your cluster: + :::caution + This strategy might miss workloads that are not currently running, such as CronJobs, workloads that scale to zero, or workloads that have not rolled out yet. + ::: + ```shell kubectl get pods \ --all-namespaces \ From ac6503f23e49fbaa216cdf0cb90ea08f545ed768 Mon Sep 17 00:00:00 2001 From: Mauren Berti <698465+stormqueen1990@users.noreply.github.com> Date: Wed, 19 Apr 2023 11:52:24 -0400 Subject: [PATCH 2/4] Change wording from "might" to "may" Change wording on the admonition from "might" to "may". --- .../pod-security-standards.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/pod-security-standards.md b/docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/pod-security-standards.md index 7e74443f907..39bea0b4cd9 100644 --- a/docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/pod-security-standards.md +++ b/docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/pod-security-standards.md @@ -25,7 +25,7 @@ You must perform the following steps _while still in Kubernetes v1.24_: 1. Map your active PSPs to Pod Security Standards: 1. See which PSPs are still active in your cluster: :::caution - This strategy might miss workloads that are not currently running, such as CronJobs, workloads that scale to zero, or workloads that have not rolled out yet. + This strategy may miss workloads that are not currently running, such as CronJobs, workloads that scale to zero, or workloads that have not rolled out yet. ::: ```shell From 7b440a3f6879e2d065bf60f7cf02c0717bac6b82 Mon Sep 17 00:00:00 2001 From: Marty Hernandez Avedon Date: Wed, 19 Apr 2023 13:16:53 -0400 Subject: [PATCH 3/4] Update docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/pod-security-standards.md --- .../pod-security-standards.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/pod-security-standards.md b/docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/pod-security-standards.md index 39bea0b4cd9..13f97c5f360 100644 --- a/docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/pod-security-standards.md +++ b/docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/pod-security-standards.md @@ -25,7 +25,7 @@ You must perform the following steps _while still in Kubernetes v1.24_: 1. Map your active PSPs to Pod Security Standards: 1. See which PSPs are still active in your cluster: :::caution - This strategy may miss workloads that are not currently running, such as CronJobs, workloads that scale to zero, or workloads that have not rolled out yet. + This strategy may miss workloads that aren't currently running, such as CronJobs, workloads that scale to zero, or workloads that haven't rolled out yet. ::: ```shell From 70eaaa1f3bf74b75be8057c5a8e25e0c0ab183dd Mon Sep 17 00:00:00 2001 From: Mauren Berti <698465+stormqueen1990@users.noreply.github.com> Date: Wed, 19 Apr 2023 13:39:21 -0400 Subject: [PATCH 4/4] Change wording on scale-to-zero Change wording to make it clear it's the workloads that are currently scaled to zero that won't be caught by the command. --- .../pod-security-standards.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/pod-security-standards.md b/docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/pod-security-standards.md index 13f97c5f360..b51d7c9759a 100644 --- a/docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/pod-security-standards.md +++ b/docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/pod-security-standards.md @@ -25,7 +25,7 @@ You must perform the following steps _while still in Kubernetes v1.24_: 1. Map your active PSPs to Pod Security Standards: 1. See which PSPs are still active in your cluster: :::caution - This strategy may miss workloads that aren't currently running, such as CronJobs, workloads that scale to zero, or workloads that haven't rolled out yet. + This strategy may miss workloads that aren't currently running, such as CronJobs, workloads currently scaled to zero, or workloads that haven't rolled out yet. ::: ```shell