Where the app writesRecordsLives as long asSo
kind: PersistentVolumeClaim
metadata: { name: data }
spec: { storageClassName: standard, accessModes: [ReadWriteOnce], resources: { requests: { storage: 5Gi } } }
---
kind: Pod      # excerpt
spec:
  volumes:
  - { name: scratch, emptyDir: {} }
  - { name: data,    persistentVolumeClaim: { claimName: data } }
Tiles: records the app has written, in the container, the emptyDir and the PVLocker lamp: the PersistentVolume is Bound to the pod's claimCable: the pod mounts the PV through its claimA container's own filesystem is thrown away whenever it restarts. An emptyDir volume belongs to the pod, so it survives container restarts but is deleted with the pod. For data that must outlive pods, a pod mounts a PersistentVolumeClaim: a request for storage of a size, access mode and class. A StorageClass provisions a PersistentVolume to satisfy the claim and binds the two. A replacement pod that uses the same claim finds the same data. When the claim is deleted, the volume's reclaimPolicy decides: Delete removes it and its data, Retain keeps it as Released for an admin to recover.
Next: StatefulSets, DaemonSets & Jobs →