Skip to content

Commit 1476ac9

Browse files
authored
Merge pull request #35618 from tallclair/psa-stable-1.25
Update Pod Security Admission docs for graduation to stable
2 parents 3261beb + 29d9fa5 commit 1476ac9

File tree

1 file changed

+5
-39
lines changed

1 file changed

+5
-39
lines changed

content/en/docs/concepts/security/pod-security-admission.md

Lines changed: 5 additions & 39 deletions
Original file line numberDiff line numberDiff line change
@@ -8,60 +8,26 @@ description: >
88
Standards.
99
content_type: concept
1010
weight: 20
11-
min-kubernetes-server-version: v1.22
1211
---
1312

1413
<!-- overview -->
1514

16-
{{< feature-state for_k8s_version="v1.23" state="beta" >}}
15+
{{< feature-state for_k8s_version="v1.25" state="stable" >}}
1716

1817
The Kubernetes [Pod Security Standards](/docs/concepts/security/pod-security-standards/) define
1918
different isolation levels for Pods. These standards let you define how you want to restrict the
2019
behavior of pods in a clear, consistent fashion.
2120

22-
As a beta feature, Kubernetes offers a built-in _Pod Security_ {{< glossary_tooltip
23-
text="admission controller" term_id="admission-controller" >}}, the successor
24-
to [PodSecurityPolicies](/docs/concepts/security/pod-security-policy/). Pod security restrictions
25-
are applied at the {{< glossary_tooltip text="namespace" term_id="namespace" >}} level when pods
26-
are created.
27-
28-
{{< note >}}
29-
The PodSecurityPolicy API is deprecated and will be
30-
[removed](/docs/reference/using-api/deprecation-guide/#v1-25) from Kubernetes in v1.25.
31-
{{< /note >}}
32-
33-
34-
## {{% heading "prerequisites" %}}
35-
36-
To use this mechanism, your cluster must enforce Pod Security admission.
21+
Kubernetes offers a built-in _Pod Security_ {{< glossary_tooltip text="admission controller"
22+
term_id="admission-controller" >}} to enforce the Pod Security Standards. Pod security restrictions
23+
are applied at the {{< glossary_tooltip text="namespace" term_id="namespace" >}} level when pods are
24+
created.
3725

3826
### Built-in Pod Security admission enforcement
3927

40-
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.
4128
This page is part of the documentation for Kubernetes v{{< skew currentVersion >}}.
4229
If you are running a different version of Kubernetes, consult the documentation for that release.
4330

44-
### Alternative: installing the `PodSecurity` admission webhook {#webhook}
45-
46-
The `PodSecurity` admission logic is also available as a [validating admission webhook](https://git.k8s.io/pod-security-admission/webhook). This implementation is also beta.
47-
For environments where the built-in `PodSecurity` admission plugin cannot be enabled, you can instead enable that logic via a validating admission webhook.
48-
49-
A pre-built container image, certificate generation scripts, and example manifests
50-
are available at [https://git.k8s.io/pod-security-admission/webhook](https://git.k8s.io/pod-security-admission/webhook).
51-
52-
To install:
53-
```shell
54-
git clone https://github.com/kubernetes/pod-security-admission.git
55-
cd pod-security-admission/webhook
56-
make certs
57-
kubectl apply -k .
58-
```
59-
60-
{{< note >}}
61-
The generated certificate is valid for 2 years. Before it expires,
62-
regenerate the certificate or remove the webhook in favor of the built-in admission plugin.
63-
{{< /note >}}
64-
6531
<!-- body -->
6632

6733
## Pod Security levels

0 commit comments

Comments
 (0)