Diegolden

Topic 2: PersistentVolumes And Claims

2 min read

Topic 2: PersistentVolumes And Claims

Official baseline: (The Kubernetes Authors, 2026). My working version: PersistentVolume is supply. PersistentVolumeClaim is demand. Binding connects app needs to storage capacity.

Mental Model

PersistentVolume is supply. PersistentVolumeClaim is demand. Binding connects app needs to storage capacity.

Notes

  • PVCs let apps request storage without knowing the backend details.
  • Reclaim policy decides what happens when claims go away.
  • Access modes are constraints, not wishes.

Homelab Angle

Before trusting a PVC, test delete, reschedule, backup, and restore. The happy path is not enough.

Verify It

  • Read the object status before changing the manifest.
  • Check events for the controller or node that is actually complaining.
  • Confirm the official source linked below still matches the cluster version you run.

Common Failure Modes

  • Treating the YAML object as the system, instead of one input to a reconciliation loop.
  • Debugging from outside the cluster when the failure only exists inside cluster networking or node state.
  • Forgetting that Kubernetes version, addon version, and runtime behavior are linked.

Sources

  • Persistent Volumes - source path: content/en/docs/concepts/storage/persistent-volumes.md, commit 8cc9e19b8eec8d5cf49eacd66f86a81648edb1a0.
  • Kubernetes documentation is licensed under CC BY 4.0; these notes are original commentary and link back to the official source.
The Kubernetes Authors. (2026). Persistent Volumes. https://kubernetes.io/docs/concepts/storage/persistent-volumes/

Graph View

Backlinks