From 9ae05ea5b387625ca6b93bb64f4738bf8e478a6d Mon Sep 17 00:00:00 2001 From: Shubham Date: Wed, 22 Jun 2022 21:05:43 +0530 Subject: [PATCH] Improvement: Clarifiy the release which include Pod Security admission by default. (#34300) * Improvement: Clarifiy the release which include Pod Security admission by default. * Modify: wrapped the long lines. --- content/en/docs/concepts/security/pod-security-admission.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/concepts/security/pod-security-admission.md b/content/en/docs/concepts/security/pod-security-admission.md index 5ced854d3a..0336e8cd54 100644 --- a/content/en/docs/concepts/security/pod-security-admission.md +++ b/content/en/docs/concepts/security/pod-security-admission.md @@ -37,8 +37,8 @@ To use this mechanism, your cluster must enforce Pod Security admission. ### Built-in Pod Security admission enforcement -In Kubernetes v{{< skew currentVersion >}}, the `PodSecurity` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) -is a beta feature and is enabled by default. You must have this feature gate enabled. +From Kubernetes v1.23, the `PodSecurity` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/)is a beta feature and is enabled by default. +This page is part of the documentation for Kubernetesv{{< skew currentVersion >}}. If you are running a different version of Kubernetes, consult the documentation for that release. ### Alternative: installing the `PodSecurity` admission webhook {#webhook}