Hands-on Lab·Certified Kubernetes Administrator
Access Modes and Reclaim Policies
Ask a node-local provisioner for ReadWriteMany and watch the claim hang. Then delete two claims: one volume is destroyed, the other becomes Released and refuses every new claimant until you clear one field by hand.
Storage Guide 70 of 103 Intermediate
- Kubernetes1.36.4
- Provisionerrancher.io/local-path
- Cluster4 nodes
- Runtimecontainerd 2.2.6
- TimeAbout 35 min
- Reviewed21 August 2026
Written against the versions above. Which access modes work depends entirely on the backend. The Released-blocks-rebinding behaviour does not.
| Server Name | IP Address | OS | Roles | CPU | RAM | HDD |
|---|---|---|---|---|---|---|
| CKA1001 | 192.168.0.175 | Ubuntu 26.04 LTS | Control Plane Node | 2 Core | 4 GB | 50 GB |
| CKA1001-NODE01 | 192.168.0.176 | Ubuntu 26.04 LTS | Worker Node | 2 Core | 4 GB | 50 GB |
| CKA1001-NODE02 | 192.168.0.177 | Ubuntu 26.04 LTS | Worker Node | 2 Core | 4 GB | 50 GB |
| CKA1001-NODE03 | 192.168.0.178 | Ubuntu 26.04 LTS | Worker Node | 2 Core | 4 GB | 50 GB |
Before you start
- The PersistentVolumes and claims guide, for the binding rules access modes participate in.
- The dynamic provisioning guide, for where
reclaimPolicy: Deletecomes from. - Permission to patch PersistentVolumes, which is a cluster-scoped operation.
-
Access modes, and asking for one the backend cannot do
-
reclaimPolicy Delete means the data is gone
-
reclaimPolicy Retain: Released, not deleted
-
A Released volume refuses every new claimant