Unused PV Detection
Lists PersistentVolumes that no Pod uses: Released, Available and never claimed, or Bound to a PVC that is gone, with capacity, reason, and estimated monthly cost.
The PVC is deleted, and the 100Gi volume stays Released, billed every month
kubernetes.io, Persistent Volumes; Wave Unused PV Detection docs. pv-abc123 and 100Gi come from the Wave docs example and are illustrative here.
With the Retain reclaim policy, "when the PersistentVolumeClaim is deleted, the PersistentVolume still exists and the volume is considered released" (kubernetes.io). An administrator reclaims it by hand.
Even after the PV object is deleted, "the associated storage asset in external infrastructure still exists" (kubernetes.io). Until someone deletes that disk too, the cloud provider bills it.
kubectl get pv shows pv-abc123, 100Gi, Released, with the claim default/database-pvc it once had. It does not show which volumes are safe to delete, or what they cost.
Released and Retain: kubernetes.io, Persistent Volumes. Detected reason and the 7-day safety period: Wave Unused PV Detection docs. pv-abc123 and 100Gi are the docs example and are illustrative.
How Wave does it
- PVCdeleted along with its app
- deletedPVthe PersistentVolume still exists, phase Released
- RetainReclaim policyRetain: reclaimed manually
- by handCluster adminfinds and deletes it by hand
- Wave Corechecks every PV once a day
- dailyPhase checkReleased, Available, or Bound with no PVC
- unusedSafety period7 days, resolved if bound again
- 7 daysWave Consolecapacity, reason, and cost per PV
Check every PV daily
Once a day, Wave checks every PersistentVolume and keeps the ones no Pod uses: Released after its PVC was deleted, Available and never claimed, or Bound to a PVC that no longer exists.
Show what each one is
Each row shows the PV name, storage class, capacity, phase, reclaim policy, access modes, and the detected reason, such as "PVC deleted but PV retains data". The view also estimates a monthly cost per PV from storage class pricing.
Wait 7 days, then decide
A PV becomes eligible for cleanup only after a 7-day safety period, and the finding is marked resolved if the PV is bound again. Detection deletes nothing, so you check the data first. The annotation waveautoscale.io/pv-cleanup="false" keeps backup PVs off the list.