[zh] Fix link for PSP
This commit is contained in:
@@ -215,7 +215,7 @@ You can also use the deprecated [PodSecurityPolicy](/docs/concepts/policy/pod-se
|
||||
to restrict users' abilities to create privileged Pods (N.B. PodSecurityPolicy is scheduled for removal
|
||||
in version 1.25).
|
||||
-->
|
||||
你还可以使用已弃用的 [PodSecurityPolicy](/zh/docs/concepts/policy/pod-security-policy/)
|
||||
你还可以使用已弃用的 [PodSecurityPolicy](/zh-cn/docs/concepts/security/pod-security-policy/)
|
||||
机制以限制用户创建特权 Pod 的能力 (特别注意:PodSecurityPolicy 已计划在版本 1.25 中删除)。
|
||||
|
||||
<!--
|
||||
@@ -235,7 +235,7 @@ PersistentVolumes, and constrained users should use PersistentVolumeClaims to ac
|
||||
-->
|
||||
### 持久卷的创建 {#persistent-volume-creation}
|
||||
|
||||
如 [PodSecurityPolicy](/zh/docs/concepts/policy/pod-security-policy/#volumes-and-file-systems)
|
||||
如 [PodSecurityPolicy](/zh-cn/docs/concepts/security/pod-security-policy/#volumes-and-file-systems)
|
||||
文档中所述,创建 PersistentVolumes 的权限可以提权访问底层主机。
|
||||
如果需要访问 PersistentVolume,受信任的管理员应该创建 `PersistentVolume`,
|
||||
受约束的用户应该使用 `PersistentVolumeClaim` 访问该存储。
|
||||
|
||||
@@ -26,7 +26,7 @@ This page describes security considerations and best practices specific to the W
|
||||
<!--
|
||||
## Protection for Secret data on nodes
|
||||
-->
|
||||
## 保护节点上的 Secret 数据
|
||||
## 保护节点上的 Secret 数据 {#protection-for-secret-data-on-nodes}
|
||||
|
||||
<!--
|
||||
On Windows, data from Secrets are written out in clear text onto the node's local
|
||||
@@ -48,7 +48,7 @@ operator, you should take both of the following additional measures:
|
||||
<!--
|
||||
## Container users
|
||||
-->
|
||||
## 容器用户
|
||||
## 容器用户 {#container-users}
|
||||
|
||||
<!--
|
||||
[RunAsUsername](/docs/tasks/configure-pod-container/configure-runasusername)
|
||||
@@ -57,7 +57,7 @@ processes as specific user. This is roughly equivalent to
|
||||
[RunAsUser](/docs/concepts/policy/pod-security-policy/#users-and-groups).
|
||||
-->
|
||||
可以为 Windows Pod 或容器指定 [RunAsUsername](/zh/docs/tasks/configure-pod-container/configure-runasusername)
|
||||
以作为特定用户执行容器进程。这大致相当于 [RunAsUser](/zh/docs/concepts/policy/pod-security-policy/#users-and-groups)。
|
||||
以作为特定用户执行容器进程。这大致相当于 [RunAsUser](/zh-cn/docs/concepts/security/pod-security-policy/#users-and-groups)。
|
||||
|
||||
<!--
|
||||
Windows containers offer two default user accounts, ContainerUser and ContainerAdministrator.
|
||||
@@ -92,7 +92,7 @@ Active Directory 身份运行。
|
||||
<!--
|
||||
## Pod-level security isolation
|
||||
-->
|
||||
## Pod 级安全隔离
|
||||
## Pod 级安全隔离 {#pod-level-security-isolation}
|
||||
|
||||
<!--
|
||||
Linux-specific pod security context mechanisms (such as SELinux, AppArmor, Seccomp, or custom
|
||||
|
||||
Reference in New Issue
Block a user