A PersistentVolumeClaim requests storage independently of any one Pod. A workload references the claim through a Pod volume, then each container mounts that volume by its local volume name. The claim name, volume name and mount path serve different purposes. A wrong claim reference can block startup, while a wrong mount path can hide the data from an otherwise running application. The local cluster supplies a small default storage model so you can inspect binding without contacting a provider. These tasks create claims and consume them, keeping application data separate from an emptyDir volume that disappears with the Pod.