Skip to content

Commit 5c9af80

Browse files
waychTim Bannister
andauthored
Update content/en/docs/concepts/security/rbac-good-practices.md
Co-authored-by: Tim Bannister <[email protected]>
1 parent cc56241 commit 5c9af80

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

content/en/docs/concepts/security/rbac-good-practices.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -128,7 +128,13 @@ to the underlying host filesystem(s) on the associated node. Granting that abili
128128
There are many ways a container with unrestricted access to the host filesystem can escalate privileges, including
129129
reading data from other containers, and abusing the credentials of system services, such as Kubelet.
130130

131-
Only trusted users should be granted permission to create PersistentVolume objects.
131+
You should only allow access to create PersistentVolume objects for:
132+
133+
- users (cluster operators) that need this access for their work, and who you trust
134+
- the Kubernetes control plane, which creates PersistentVolumes based on PersistentVolumeClaims
135+
that are configured for automatic provisioning.
136+
(Kubernetes usually sets up that access for the control plane when you deploy a cluster).
137+
132138
Where access to persistent storage is required trusted administrators should create
133139
PersistentVolumes, and constrained users should use PersistentVolumeClaims to access that storage.
134140

0 commit comments

Comments
 (0)