Persistent volume claim
A PersistentVolumeClaim is a Kubernetes resource through which a workload requests persistent storage with specified capacity, access modes, and other storage characteristics.
Kubernetes in Action, Second Edition
A persistentVolumeClaim volume is a pod volume definition that references a PersistentVolumeClaim by name.
- How it is used
- Connects a pod to persistent storage through a named PersistentVolumeClaim rather than a direct PersistentVolume reference.
- How deep it goes
- Shows the pod fields, container mount, and binding checks; leaves storage provisioning to the claim, StorageClass, and provisioner.
- Examples
- Uses a quiz pod manifest that mounts a claimed volume into MongoDB, followed by `kubectl get pvc` and `kubectl get pv` checks.
- What you can do after
- Apply it via a pod manifest to mount an existing claim, then verify that the claim and volume are bound.
Read how Kubernetes in Action, Second Edition explains persistent volume claim →
Kubernetes for Developers
A PersistentVolumeClaim is a Kubernetes storage request that allows a workload to obtain persistent storage with specified capacity and access properties.
- How it is used
- Requests persistent storage for stateful Pods without tying their specifications directly to a cloud disk.
- How deep it goes
- Works through claim fields, PV binding, inspection, reclaim policies, and recovery rather than stopping at the API definition.
- Examples
- Uses a MariaDB data mount, bound-object kubectl output, StatefulSet claim templates, and a Redis disk-recovery exercise.
- What you can do after
- Operate/configure it by requesting storage, checking PV binding, choosing retention, and using per-Pod claims for StatefulSet replicas.
Read how Kubernetes for Developers explains persistent volume claim →
Acing the Certified Kubernetes Administrator Exam, Second Edition
A persistent volume claim is a Kubernetes object that requests and reserves storage from a persistent volume.
- How it is used
- Reserves persistent storage for a pod and provides the claim used when mounting that storage in a workload.
- How deep it goes
- Works through claim binding, capacity matching, verification, and deletion behavior without detailing storage-provider internals.
- Examples
- Uses a 90 MB claim bound to a 100 MB hostPath volume, plus kubectl output showing binding and blocked deletion.
- What you can do after
- Build it from scratch by creating a claim, mounting it in a workload, and verifying the bound volume with kubectl.
Google Anthos in Action
A PersistentVolumeClaim is a Kubernetes resource through which a workload requests storage with specified capacity and access properties.
- How it is used
- Connects stateful or data-oriented workloads with requested durable storage in generated Kubernetes deployment specifications.
- How deep it goes
- Defines the claim as a request for a PersistentVolume and identifies capacity and access mode, without detailing binding mechanics.
- Examples
- Uses generated Migrate for Anthos YAML for stateful applications and data deployments.
- What you can do after
- Evaluate how a workload requests durable storage by specifying capacity and access properties.
Read how Google Anthos in Action explains persistent volume claim →
Effective Platform Engineering
A persistent volume claim is a Kubernetes resource that requests persistent storage with specified capacity and access requirements.
- How it is used
- Tests Kubernetes storage integration by provisioning, mounting, writing, and expanding claims.
- How deep it goes
- Demonstrates manifests and executable checks but stops short of explaining claim-binding internals.
- Examples
- Uses EBS ReadWriteOnce and EFS ReadWriteMany claims with mounted pods, timestamp files, Bats checks, and capacity expansion.
- What you can do after
- Diagnose storage integration by verifying binding, pod health, write access, shared writes, and claim expansion.
Read how Effective Platform Engineering explains persistent volume claim →
Distributed Machine Learning Patterns
A PersistentVolumeClaim is a Kubernetes resource that requests persistent storage with specified capacity and access requirements.
- How it is used
- Preserves datasets, checkpoints, and trained models across distributed-training Pods and sequential workflow steps.
- How deep it goes
- Defines capacity, access modes, PV relationships, and mounting, but does not detail storage-backend administration.
- Examples
- Uses a 1 Gi ReadWriteOnce claim mounted at /trained_model by two-worker training and later workflow steps.
- What you can do after
- Operate/configure persistent training storage by creating a PVC and mounting it in Kubernetes workloads.
Read how Distributed Machine Learning Patterns explains persistent volume claim →
Road to Kubernetes
A PersistentVolumeClaim is a Kubernetes resource that requests storage with specified capacity, access modes, and storage class properties.
- How it is used
- Requests cloud-managed storage for Pods and supplies that storage to a Deployment.
- How deep it goes
- Defines core manifest fields, provider limitations, lifecycle choices, attachment, application, and verification.
- Examples
- Uses a 10Gi nginx claim, a ReadWriteOnce access mode, volume mounting, kubectl application, and PVC inspection.
- What you can do after
- Operate/configure a PVC, attach it to a Deployment, apply the manifests, and inspect the resulting claim.
Read how Road to Kubernetes explains persistent volume claim →
Machine Learning Platform Engineering
A persistent volume claim is a Kubernetes resource that requests storage with specified capacity and access characteristics for use by workloads.
- How it is used
- Supports shared, persistent dataset and log storage across Kubeflow pipeline components and notebook workloads.
- How deep it goes
- Explains PVC creation, capacity, access modes, mounting, ordering, and downstream simplification without detailing storage-controller internals.
- Examples
- Uses notebook volumes, a YOLO pipeline, dataset splitting, model training, model validation, and TensorBoard log access.
- What you can do after
- Build shared pipeline storage by creating, mounting, sequencing, and reusing a PVC across Kubeflow components.
Read how Machine Learning Platform Engineering explains persistent volume claim →
Data Pipelines with Apache Airflow, Second Edition
A persistent volume claim is a Kubernetes resource request for persistent storage with specified capacity and access requirements.
- How it is used
- Provides persistent storage for data produced by Airflow tasks running in Kubernetes pods.
- How deep it goes
- Defines capacity and access settings, demonstrates deployment, and diagnoses pending pods, but does not detail storage backends.
- Examples
- Uses a 1Gi data-volume claim, ReadWriteOnce access, a local hostPath, kubectl apply, and pod Events.
- What you can do after
- Operate/configure Kubernetes storage for Airflow pods and diagnose scheduling failures caused by missing or unbound claims.
Read how Data Pipelines with Apache Airflow, Second Edition explains persistent volume claim →
Related concepts
- persistent volumeuses · A persistent volume is durable storage provisioned independently of an individual workload’s lifecycle, allowing data to survive workload replacement or restart.
- podused by · A Kubernetes Pod is the smallest deployable unit in Kubernetes, grouping one or more co-located containers that share networking and other resources.
- StatefulSetproduced by · A StatefulSet is a Kubernetes workload resource that manages stateful Pods with stable identities, ordered operations, and persistent storage associations.
- StorageClassuses · A StorageClass is a Kubernetes API resource that defines a category of storage and the provisioner and parameters for dynamically creating volumes.
- TensorBoardused by · TensorBoard is a web-based tool for visualizing and monitoring machine-learning experiments and their logged data, including metrics, model graphs, and other run information.
- Kubernetes controllerproduced by · A Kubernetes controller is a control-loop component that observes resource state and takes action to move actual state toward desired state.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.