Fix the feature state of PodSecurity (zh-cn) (#36895)

Co-authored-by: amolmote <amolmote201@gmail.com>
pull/37081/head
houjun 2022-09-29 19:56:54 +08:00 committed by GitHub
parent b78f244acb
commit 40c2a56157
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions

View File

@ -444,7 +444,7 @@ name as the key. This admission controller, if enabled, automatically
adds tolerations for such taints to pods requesting extended resources, so users don't have to manually
add these tolerations.
This admission controller is diabled by default.
This admission controller is disabled by default.
-->
此插件有助于创建带有扩展资源的专用节点。
如果运维人员想要创建带有扩展资源(如 GPU、FPGA 等)的专用节点,他们应该以扩展资源名称作为键名,
@ -595,7 +595,7 @@ any pod annotations that match `*.image-policy.k8s.io/*`.
`imagepolicy.k8s.io/v1alpha1` `ImageReview` 对象。
该对象包含描述被准入容器的字段,以及与 `*.image-policy.k8s.io/*` 匹配的所有 Pod 注解。
{{ note }}
{{< note >}}
<!--
The webhook API objects are subject to the same versioning compatibility rules
as other Kubernetes API objects. Implementers should be aware of looser compatibility
@ -609,7 +609,7 @@ group (`--runtime-config=imagepolicy.k8s.io/v1alpha1=true`).
以确保正确的反序列化。
此外API 服务器必须启用 `imagepolicy.k8s.io/v1alpha1` API 扩展组
`--runtime-config=imagepolicy.k8s.io/v1alpha1=true`)。
{{ /note }}
{{< /note >}}
<!--
An example request body:
@ -1091,7 +1091,7 @@ PodNodeSelector 允许 Pod 强制在特定标签的节点上运行。
### PodSecurity {#podsecurity}
{{< feature-state for_k8s_version="v1.23" state="beta" >}}
{{< feature-state for_k8s_version="v1.25" state="stable" >}}
<!--
This is the replacement for the deprecated [PodSecurityPolicy](#podsecuritypolicy) admission controller