As our Kubernetes exploration moves from simple demo workloads to real applications, we inevitably face a crucial question: what happens to our data when pods are created, destroyed, or rescheduled? A container restart is harmless for a stateless web front end, but it becomes catastrophic for a database, a file-sharing service, or an AI pipeline that depends on durable data.