Kubernetes v1.37 Promotes PVC Last Used Time Tracking Feature to Beta by Default
Kubernetes v1.37 has promoted the PersistentVolumeClaimUnusedSinceTime feature to Beta and enabled it by default, allowing cluster administrators to easily identify unused persistent volumes and optimize storage costs.
In Kubernetes v1.37, the PersistentVolumeClaimUnusedSinceTime feature has transitioned to Beta and is now active by default. This enhancement enables the PVC Protection Controller to dynamically update each PersistentVolumeClaim with an Unused status condition. This condition clearly indicates whether a running Pod is actively referencing the PVC, simplifying storage hygiene in busy environments.
Primary source
Open Kubernetes Blog ↗This article summarizes the source. Check the original for full details and conditions.
Comparison
| Aspect | Before / Alternative | After / This |
|---|---|---|
| Unused PVC Identification | Manual cross-referencing of active Pod definitions against PVC lists or using custom scripts | Native PVC status tracking via standard Kubernetes API conditions |
| Idle Duration Tracking | Imprecise estimation based on Pod deletion events in external log aggregators | Direct assessment using the lastTransitionTime property in the PVC status conditions |
| Automation Overhead | High operational effort to build, secure, and maintain in-house storage cleanup utilities | Low operational effort, relying on built-in controller flags and native API fields |
Action Checklist
- Upgrade clusters to Kubernetes version 1.37 or newer to enable the feature automatically. The feature gate is active by default in the beta release.
- Query PVCs for the Unused condition using kubectl or API requests. Look specifically for the lastTransitionTime field under the status.conditions block.
- Integrate the lastTransitionTime metric into automated storage reclaiming pipelines. Verify safety thresholds before auto-deleting long-unused PersistentVolumeClaims.