Kubernetes v1.37 Beta Introduces PersistentVolumeClaim Unused Tracking

New Feature in Kubernetes v1.37

Kubernetes v1.37 has promoted the PersistentVolumeClaimUnusedSinceTime feature gate to Beta, making it enabled by default. This enhancement introduces an "Unused" condition to PersistentVolumeClaims (PVCs), providing a native way to track whether a PVC is currently referenced by any running pod within a cluster.

Addressing Orphaned PVCs

In large Kubernetes environments, it is common for users to create PVCs and then delete associated pods without subsequently removing the storage. Kubernetes does not automatically delete PVCs upon pod removal to prevent accidental data loss. Over time, these orphaned PVCs can accumulate, leading to wasted storage capacity and increased cloud infrastructure costs.

Improved PVC Usage Visibility

Previously, determining if a PVC was still in use required complex manual cross-referencing of pods, PersistentVolumes, and PVCs, often necessitating custom monitoring tools or scripts. The new "Unused" condition, managed by the PVC protection controller, simplifies this process by making the usage status directly available within the PVC's status. This allows storage administrators and DevOps engineers to easily identify and automate the cleanup of unneeded volumes.

How the Unused Condition Works

The PVC protection controller, which already monitors pods for storage object in-use protection, now also manages the new "Unused" condition on PVCs. A PVC is marked as "Unused=True" if no running pod references it. Notably, terminated pods (those with phase Succeeded or Failed) do not keep a PVC marked as in use, meaning batch jobs will not prevent a PVC from becoming unused after completion. However, pending pods, even those that are unschedulable, still count as using the PVC, reflecting an intent to use the volume.