PricingPricingDocsDocsBlogBlogBook a demoBook a demoCompanyCompany (opens in a new tab)
Product
DocsAPI ReferencePricingConsole DemoBlogCompany
Start Freev3.4.7
Platform & Observability

PV Cleanup

Deletes PersistentVolume objects that no PVC uses, only after every protection check passes and only when you turn cleanup on, and logs each deletion.

The challenge

The PVC was deleted 30 days ago. Its 100Gi PV still shows Released.

kubernetes.io, Persistent Volumes; Wave Auto Clean Up docs. 30 days and 100Gi are illustrative.

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.

Wave cleanup is off by default. When you turn it on, it deletes only PVs that pass every protection check: no custom finalizer, no opt-out annotation, no existing PVC, and no VolumeAttachment.

Deleting the PV object is not the same as deleting the disk. Under Retain, "the associated storage asset in external infrastructure still exists after the PV is deleted" (kubernetes.io). Check the disk with your storage provider.

A Released PV that stays, then a PV that is checked and deletedWithout WaveWith WaveReleased✓Released, stayschecked, deleted
Without Wave
Retain: the PV stays ReleasedBoundPVC: data-db-0PVC deletedReleasedRetain · 100Gistays ReleasedRetain: Kubernetes deletes nothing.An admin finds it and deletes it by hand.
The PVC was deleted, and with the Retain policy the PV stays Released. Kubernetes does nothing more until an admin reclaims it by hand.
With Wave
Wave checks each unused PV, then deletes the PV objectDetect unusedReleased PVProtectionchecks passDelete PVobject onlyprotectedInProgressCompletedOnly when cleanup is on. Off by default.The disk: check your storage provider.
Wave detects the unused PV, runs the protection checks, and deletes the PV object when cleanup is on. Under Retain the disk may still exist (kubernetes.io), so check it with your storage provider.

Released, Retain, and the storage asset: kubernetes.io, Persistent Volumes. Protection checks, the cleanup switch, and the statuses: Wave Auto Clean Up docs. data-db-0 and 100Gi are illustrative.

How Wave does it

From a Released PV to a deleted PV object
Kubernetes, RetainStays until someone acts
  1. PVC
    deleted along with its app
  2. ↓Retain→
    PV
    still exists, phase Released
  3. ↓waits→
    Cluster admin
    finds it and deletes it by hand
  4. ↓by hand→
    Storage asset
    still exists after the PV is deleted
PV CleanupPV object deleted and logged
  1. Wave Core
    scans every PV: Released, Available, or orphaned
  2. ↓unused→
    Protection checks
    finalizer, annotation, PVC, attachment
  3. ↓eligible→
    Cleanup switch
    off by default; you turn it on
  4. ↓delete→
    Kubernetes API
    PV deleted, logged InProgress, then Completed
Default lane: kubernetes.io (Persistent Volumes). Wave lane: Wave Auto Clean Up docs.
1

Review the list first

Detection runs even while cleanup is off. Unused PV Detection lists each Released, Available, or orphaned PV with its reason, so you can check the list before anything is deleted.

2

Protect what must stay

Add waveautoscale.io/pv-cleanup: disabled to a PV, or to a StorageClass to protect every PV that uses it. PVs with a custom finalizer, such as velero.io/*, are never marked unused.

3

Turn cleanup on

Turn on Enable Auto Cleanup in Storage, PV Auto Cleanup. For each eligible PV, Wave calls the Kubernetes delete API and logs it as InProgress, then Completed or Failed.

Related in Platform & Observability

Programmable API →SSO (OIDC) →PV Auto-Expansion →Alerts →Cluster Map →Prometheus & Grafana Integration →Read the docs →
Book a demoStart free
Product
Wave GPUAI Infrastructure Professional ServiceWaveWave AI Agent2026 Q4
Resources
DocsAPI ReferenceBlogConsole DemoPricing
Company
STCLabBook a demoContact
STCLab© 2026 Wave All rights reserved.
Terms of ServicePrivacy PolicyCookies