Volumes vs Persistent Volumes in Kubernetes - Visual Side-by-Side Comparison

Process Flow - Volumes vs Persistent Volumes

Pod starts

↓

Volume attached

↓

Data stored temporarily

↓

Pod stops -> Volume lost

↓

Persistent Volume created

↓

Pod claims Persistent Volume

↓

Data stored persistently

↓

Pod stops -> Data remains intact

Shows how normal Volumes exist only during pod life, while Persistent Volumes keep data beyond pod life.

Execution Sample

Kubernetes

apiVersion: v1
kind: Pod
metadata:
  name: example-pod
spec:
  volumes:
  - name: temp-volume
    emptyDir: {}
  containers:
  - name: app
    image: busybox
    volumeMounts:
    - mountPath: /data
      name: temp-volume

Defines a pod with a temporary volume (emptyDir) that lasts only while the pod runs.

Process Table

Step	Action	Volume Type	Data Persistence	Result
1	Pod starts	emptyDir Volume	Data stored temporarily	Volume created and mounted to pod
2	Write data inside pod at /data	emptyDir Volume	Data available during pod life	Data written successfully
3	Pod stops	emptyDir Volume	Data lost after pod stops	Volume deleted, data lost
4	PersistentVolume created by admin	Persistent Volume	Data stored persistently	Volume ready for claim
5	Pod claims PersistentVolume via PersistentVolumeClaim	Persistent Volume	Data persists beyond pod life	Volume mounted to pod
6	Write data inside pod at mounted path	Persistent Volume	Data saved persistently	Data written successfully
7	Pod stops	Persistent Volume	Data remains intact	Volume still exists with data

💡 Pod lifecycle ends; emptyDir volume data lost, Persistent Volume data remains.

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 6	After Step 7
emptyDir Volume Data	none	data present	lost (none)	n/a	n/a
Persistent Volume Data	none	n/a	n/a	data present	data present

Key Moments - 3 Insights

Why does data in emptyDir volume disappear after pod stops?

Because emptyDir volumes exist only during pod life, as shown in execution_table step 3 where pod stops and data is lost.

How does Persistent Volume keep data after pod stops?

Persistent Volumes are independent resources that exist beyond pod lifecycle, shown in steps 4-7 where data remains after pod stops.

Can multiple pods share the same Persistent Volume?

Yes, Persistent Volumes can be shared if configured, unlike emptyDir which is pod-specific. This is implied by Persistent Volume being separate from pod lifecycle.

Visual Quiz - 3 Questions

Look at the execution table, what happens to data in emptyDir volume at step 3?

A Data is lost because pod stops

B Data is saved permanently

C Data is copied to Persistent Volume

D Data is backed up automatically

💡 Hint

Check execution_table row for step 3 under 'Result' and 'Data Persistence'

At which step does the pod claim a Persistent Volume?

A Step 2

B Step 5

C Step 1

D Step 7

💡 Hint

Look at execution_table 'Action' column for pod claiming Persistent Volume

If the pod using emptyDir volume restarts, what happens to the data?

A Data is moved to Persistent Volume automatically

B Data remains intact after restart

C Data is lost and volume is recreated

D Pod cannot restart with emptyDir volume

💡 Hint

Refer to variable_tracker for emptyDir Volume Data after pod stops (step 3)

Concept Snapshot

Volumes in Kubernetes are temporary storage tied to pod life (e.g., emptyDir).
Persistent Volumes are independent storage resources that keep data beyond pod lifecycle.
Pods use PersistentVolumeClaims to access Persistent Volumes.
emptyDir data is lost when pod stops; Persistent Volume data remains.
Use Persistent Volumes for important data needing durability.

Full Transcript

This visual execution compares Kubernetes Volumes and Persistent Volumes. When a pod starts, it can use a Volume like emptyDir which stores data temporarily. Data written to emptyDir is lost when the pod stops, as shown in step 3 of the execution table. In contrast, Persistent Volumes are created separately and exist beyond pod life. Pods claim Persistent Volumes via PersistentVolumeClaims, mount them, and write data that persists even after the pod stops, demonstrated in steps 4 to 7. The variable tracker shows emptyDir data disappears after pod stops, while Persistent Volume data remains. Key moments clarify why emptyDir data is lost and how Persistent Volumes provide durable storage. The quiz tests understanding of these lifecycle differences and data persistence behaviors.