| 1 | Persistent storage in Kubernetes is a three-resource contract. On the left stack, the Pod claims storage by naming a PersistentVolumeClaim, the PVC requests size and access mode, and the PersistentVolume represents a concrete backing disk — a cloud volume, an NFS share, or any storage backend. On the right side, the admin defines a StorageClass — a recipe — and a CSI driver implements it. When dynamic provisioning is enabled, a PVC request triggers the StorageClass to create a fresh PV on demand. The access modes ReadWriteOnce, ReadOnlyMany, ReadWriteMany, and ReadWriteOncePod control how many nodes or Pods can mount the volume, and the reclaim policy decides what happens to the data when the PVC is deleted. |