Skip to content

Commit f6abf85

Browse files
authored
Merge pull request #39076 from windsonsea/rbacpra
[zh] sync rbac-good-practices.md
2 parents 522fdf9 + 32d54ec commit f6abf85

File tree

1 file changed

+32
-8
lines changed

1 file changed

+32
-8
lines changed

content/zh-cn/docs/concepts/security/rbac-good-practices.md

Lines changed: 32 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -238,17 +238,41 @@ considered weak.
238238
<!--
239239
### Persistent volume creation
240240
241-
As noted in the [PodSecurityPolicy](/docs/concepts/security/pod-security-policy/#volumes-and-file-systems)
242-
documentation, access to create PersistentVolumes can allow for escalation of access to the underlying host.
243-
Where access to persistent storage is required trusted administrators should create
244-
PersistentVolumes, and constrained users should use PersistentVolumeClaims to access that storage.
241+
If someone - or some application - is allowed to create arbitrary PersistentVolumes, that access
242+
includes the creation of `hostPath` volumes, which then means that a Pod would get access
243+
to the underlying host filesystem(s) on the associated node. Granting that ability is a security risk.
245244
-->
246245
### 持久卷的创建 {#persistent-volume-creation}
247246

248-
[PodSecurityPolicy](/zh-cn/docs/concepts/security/pod-security-policy/#volumes-and-file-systems)
249-
文档中所述,创建 PersistentVolumes 的权限可以提权访问底层主机。
250-
如果需要访问 PersistentVolume,受信任的管理员应该创建 `PersistentVolume`
251-
受约束的用户应该使用 `PersistentVolumeClaim` 访问该存储。
247+
如果允许某人或某个应用创建任意的 PersistentVolume,则这种访问权限包括创建 `hostPath` 卷,
248+
这意味着 Pod 将可以访问对应节点上的下层主机文件系统。授予该能力会带来安全风险。
249+
250+
<!--
251+
There are many ways a container with unrestricted access to the host filesystem can escalate privileges, including
252+
reading data from other containers, and abusing the credentials of system services, such as Kubelet.
253+
254+
You should only allow access to create PersistentVolume objects for:
255+
-->
256+
不受限制地访问主机文件系统的容器可以通过多种方式提升特权,包括从其他容器读取数据以及滥用系统服务(例如 Kubelet)的凭据。
257+
258+
你应该只允许以下实体具有创建 PersistentVolume 对象的访问权限:
259+
260+
<!--
261+
- users (cluster operators) that need this access for their work, and who you trust,
262+
- the Kubernetes control plane components which creates PersistentVolumes based on PersistentVolumeClaims
263+
that are configured for automatic provisioning.
264+
This is usually setup by the Kubernetes provider or by the operator when installing a CSI driver.
265+
-->
266+
- 需要此访问权限才能工作的用户(集群操作员)以及你信任的人,
267+
- Kubernetes 控制平面组件,这些组件基于已配置为自动制备的 PersistentVolumeClaim 创建 PersistentVolume。
268+
这通常由 Kubernetes 提供商或操作员在安装 CSI 驱动程序时进行设置。
269+
270+
<!--
271+
Where access to persistent storage is required trusted administrators should create
272+
PersistentVolumes, and constrained users should use PersistentVolumeClaims to access that storage.
273+
-->
274+
在需要访问持久存储的地方,受信任的管理员应创建 PersistentVolume,而受约束的用户应使用
275+
PersistentVolumeClaim 来访问该存储。
252276

253277
<!--
254278
### Access to `proxy` subresource of Nodes

0 commit comments

Comments
 (0)