Explain the difference between an emptyDir volume and a PersistentVolumeClaim.

• A. emptyDir is ephemeral to the Pod lifetime; PVC uses a PV for persistent storage across restarts.
• B. emptyDir persists across Pod termination; PVC does not persist.
• C. emptyDir is for network policies; PVC stores images.
• D. emptyDir is a type of secret; PVC is a type of config map.

Answer: (A)

At a glance, emptyDir provides temporary, node-local storage that lasts only for the life of the Pod. When the Pod is scheduled on a node, an emptyDir volume is created and backed by that node’s filesystem. The moment the Pod is deleted or recreated, the data in that volume is gone, and if the Pod moves to another node, there’s no guarantee the data travels with it. It’s ideal for scratch space, caches, or data that only needs to exist while the Pod is running, or for sharing data between containers inside the same Pod.

A PersistentVolumeClaim, by contrast, is a request for durable storage not tied to a single Pod. It binds to a PersistentVolume, which is a piece of storage in the cluster that can be backed by networked or cloud storage (like NFS, AWS EBS, Google Cloud PD, etc.). The data on a PV persists beyond the lifetime of any one Pod, so Pods can be started, stopped, or moved and still access the same data. The reclaim policy of the PV also determines what happens to the storage when the PVC is deleted, enabling true long-term persistence.

So, emptyDir is for ephemeral, Pod-scoped storage, while a PVC provides persistent storage that survives Pod restarts and rescheduling. The other concepts mentioned (like secrets, config maps, or network policies) don’t correspond to storage volumes for data persistence.