Decide who may write a claim, where it can bind, when growth becomes usable, and whether a deletion reaches the backing asset. Confirm the application result and recovery path, not only the Kubernetes object phase.
Review these lessons
- ReadWriteOncePod: enforce one Kubernetes writer for one claim
- Delayed volume binding: choose storage topology with the first Pod
- PVC expansion: verify both backing volume and usable filesystem
- PV reclaim policy: trace the real asset before deleting a claim
- StatefulSet PVC retention: separate scale-down from deletion
- Volume ownership changes: keep fsGroup from turning recovery into a long mount
- Raw block PVCs: make the application's formatting responsibility explicit
- Local PVs: plan for node loss as a data-location failure
Other checks
Common Mistakes
- Do not infer single-Pod safety from a node-level access mode.
- Do not delete a claim before checking its bound PV policy.