PV reclaim policy: trace the real asset before deleting a claim

Last updated: 7 Oct 20266 min read

tutorial

A PersistentVolume's reclaim policy determines what happens after its claim is released. Delete can remove the PV and its backing storage asset when the provisioner supports deletion. Retain leaves the released asset for an administrator to reclaim manually. The StorageClass supplies a policy to newly provisioned PVs, but the live PV's policy is the value that matters during an actual claim deletion. A retained disk is not automatically a usable backup.

Operational decision

A checkout namespace is being retired while receipt archives must remain available for seven more months. Identify the claim, bound PV, provider volume ID, reclaim policy, snapshots, encryption key, and documented owner. Confirm the live PV is set to Retain before deleting the claim, then rehearse in a disposable namespace. Observe the released PV and cloud asset after deletion; store its identifiers in a restricted handoff record. Test reattachment through a separate recovery claim or approved restore path rather than assuming a Released PV can be claimed without manual preparation. If Delete is intended for ephemeral review data, verify the provider asset actually disappears and no customer records were copied into it. A finalizer may delay object deletion while in use; investigate the active reference instead of removing protection blindly. Review class defaults when creating new workloads, because an omitted policy may not match the retention requirement.

kubectl -n checkout get pvc receipt-archive -o wide
kubectl get pv -o custom-columns=NAME:.metadata.name,CLAIM:.spec.claimRef.name,POLICY:.spec.persistentVolumeReclaimPolicy,STATUS:.status.phase

Cost and verification

Retain prevents automatic deletion but leaves storage billing, access-control, and erasure work to operators. Delete reduces orphan cost but can remove the only copy if the recovery plan was assumed rather than tested. Measure released volumes with no owner, assets deleted outside the retention window, and time to restore a retained claim. A snapshot or retained PV can still be unusable if its encryption key is gone or its data is inconsistent.

Common Mistakes

Do not infer the live PV policy solely from the current StorageClass definition.
Do not call a retained disk a tested backup.
Do not remove protection finalizers just to make a deletion command finish.

Connected lessons

Practice and check

devops

operations