Reclaim policy
A reclaim policy is a Kubernetes storage setting determining what happens to a PersistentVolume and its underlying storage after its claim is released.
Kubernetes for Developers
A reclaim policy is a Kubernetes storage setting that determines what happens to underlying storage after its persistent volume is released.
- How it is used
- Determines whether a dynamically provisioned disk is removed or preserved when its claim is deleted.
- How deep it goes
- Explains both policy choices and shows StorageClass configuration, PV inspection, and a disk-recovery procedure.
- Examples
- Uses StorageClass YAML, Redis disk recovery, and a scratch-volume Pod to contrast Retain with Delete.
- What you can do after
- Operate/configure it by selecting a StorageClass policy, checking a PV, and preserving a disk for later recovery.
Read how Kubernetes for Developers explains reclaim policy →
Kubernetes in Action, Second Edition
The reclaimPolicy field is a StorageClass configuration field that sets the reclaim policy for provisioned PersistentVolumes.
- How it is used
- Controls whether storage is retained or deleted when a PersistentVolumeClaim releases its PersistentVolume.
- How deep it goes
- Explains policy values, lifecycle states, defaults, reuse, and policy changes, but does not show a complete StorageClass manifest.
- Examples
- Uses kubectl deletion and inspection commands to show a volume changing from Bound to Released.
- What you can do after
- Operate/configure storage retention safely and identify when claim deletion may destroy underlying data.
Read how Kubernetes in Action, Second Edition explains reclaim policy →
Acing the Certified Kubernetes Administrator Exam, Second Edition
A reclaim policy specifies what Kubernetes does with a persistent volume after its persistent volume claim is released.
- How it is used
- Controls persistent-volume cleanup or preservation after a claim is released.
- How deep it goes
- Explains three policy outcomes, identifies deprecated Recycle, and names supported Delete backends.
- Examples
- Uses kubectl describe output for vol02833 and a PV, PVC, and pod persistence exercise.
- What you can do after
- Operate/configure PV lifecycle behavior and verify the selected policy with kubectl describe.
Read how Acing the Certified Kubernetes Administrator Exam, Second Edition explains reclaim policy →
Related concepts
- retain policyincludes · A Retain policy preserves a persistent volume and its underlying storage after its claim is released or deleted.
- deletionincludes · Deletion is an operation that removes an item, association, or resource from a collection or system, or requests or marks it for removal.
- StorageClassconfigures · A StorageClass is a Kubernetes API resource that defines a category of storage and the provisioner and parameters for dynamically creating volumes.
- dynamic provisioningused by · Dynamic provisioning is the automatic creation of persistent storage resources in response to compatible storage requests.
- persistent volumeconfigures · A persistent volume is durable storage provisioned independently of an individual workload’s lifecycle, allowing data to survive workload replacement or restart.
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.