reclaim policy
The setting that decides what happens to a volume's real storage when its claim is deleted: Delete removes it, Retain keeps it.
With Delete, removing a claim destroys the data it held.
In more detail
Dynamically provisioned volumes inherit the policy from their StorageClass, often Delete. Retain protects data from an accidental claim deletion but leaves cleanup to an administrator.
Related terms
- StorageClass — A cluster-wide policy that tells Kubernetes how to create new volumes on demand: which driver, which settings, and what happens on delete.
- PersistentVolume — A cluster-scoped object representing a piece of real storage, such as a cloud disk, that a claim can bind to.
Taught in
- StorageClasses: Why A Claim Waits For Its Pod — Certified Kubernetes Administrator (CKA) Exam Prep
- Volumes By Hand: Access Modes, Binding And Reclaim — Certified Kubernetes Administrator (CKA) Exam Prep
- Volumes, PersistentVolumes And PersistentVolumeClaims — Kubernetes: Production-Grade Container Orchestration
- StorageClasses, CSI And Dynamic Provisioning — Kubernetes: Production-Grade Container Orchestration
- Troubleshooting: Pending Claims And Failed Mounts — Kubernetes: Production-Grade Container Orchestration