Understanding Kubernetes: Part 11 -Persistent Volume (PV)

If you’ve been following our Kubernetes series 2025, welcome back! For new readers, check out Part 10: Understanding Kubernetes: StorageClass

📖 Not a Medium member? No worries! Here’s the free link: Part 11-StorageClass

What is a Persistent Volume (PV) in Kubernetes?

A Persistent Volume (PV) in Kubernetes is a storage resource that exists independently of pods and provides a way to store data persistently. Unlike ephemeral pod storage, a PV allows data to persist even if the pod is deleted or restarted. It abstracts the underlying storage system, such as NFS, AWS EBS, or local disks, and provides a unified way to manage storage in Kubernetes.

For example:

If you have an application that requires a database, like MySQL, the database data must be retained across restarts. A Persistent Volume ensures that the data is stored on durable storage, allowing the database to recover its state after any disruption.

Persistent Volume Capabilities:

• Abstraction: Supports multiple storage backends (e.g., local disks, cloud storage).
• Decoupled from Pods: A PV exists independently of pods, providing persistent storage.