Persistent Volume Claim (PVC)

A Persistent Volume Claim is a request for storage resources within Kubernetes. It abstracts underlying storage systems and allows pods to consume persistent storage dynamically.

Part of the imported glossary archive.

A Persistent Volume Claim (PVC) is a Kubernetes object that requests storage for an application. It separates storage consumption from storage provisioning, allowing pods to use persistent data without depending on specific infrastructure details. This abstraction makes storage management more portable and consistent across environments.

How It Works

In Kubernetes, storage administrators define Persistent Volumes (PVs), which represent available storage resources such as block storage, NFS shares, or cloud disks. A claim specifies required characteristics like storage size, access mode, and storage class. Kubernetes then binds the request to a matching volume automatically.

Applications reference the claim instead of the underlying storage system directly. When a pod starts, Kubernetes mounts the associated volume into the container filesystem. Data written to the mounted path persists even if the pod restarts, moves to another node, or gets recreated during deployments.

Dynamic provisioning simplifies this process further. With a configured StorageClass, Kubernetes can create storage on demand through cloud or infrastructure APIs. This removes the need for administrators to pre-create every volume manually and supports scalable, automated operations.

Why It Matters

Stateful workloads such as databases, message queues, analytics systems, and monitoring platforms require durable storage. Without persistent storage, application data disappears when containers terminate. Claims provide a standardized way to manage this requirement across clusters and cloud providers.

For operations teams, this model improves portability and reduces infrastructure coupling. Developers request storage through Kubernetes-native objects while platform teams control backend storage policies separately. This separation supports automation, policy enforcement, backup strategies, and predictable scaling in production environments.

PVCs also help teams adopt GitOps and Infrastructure as Code practices because storage requirements become declarative and version-controlled alongside application manifests.

Key Takeaway

A PVC gives Kubernetes workloads reliable, portable, and infrastructure-agnostic persistent storage through a simple declarative request model.