# Kubernetes v1.37: Tracking When a PersistentVolumeClaim Was Last Used (Beta)

Publisher-attributed story with a reviewed brief or permitted publisher paragraph. The original publisher is responsible for the linked reporting.

- Publisher: Kubernetes
- Category: Infrastructure
- Original publication time: 2026-09-21T18:30:00Z
- First observed by NexusTechWire: 2026-10-01T15:54:35Z
- Original source: https://kubernetes.io/blog/2026/09/21/kubernetes-v1-37-pvc-last-used-time/
- NexusTechWire record: https://nexustechwire.com/news/news-206c285589f14136ad72

## From the publisher

Kubernetes v1.37 promotes the PersistentVolumeClaimUnusedSinceTime feature gate to Beta (enabled by default). With this feature, the PersistentVolumeClaim (PVC) protection controller adds an Unused condition to each PVC, telling you whether any running pod currently references it — no custom tooling or cross-referencing required. For the API definition of PVC conditions, see the PersistentVolumeClaim API reference. Read on to learn how the Unused condition works and how to use it. Why track PVC usage? In large-scale Kubernetes clusters, it is common for users to create PVCs and then delete the associated pods without cleaning up the storage, because Kubernetes does not automatically delete PVCs when their pods are removed (to protect against accidental data loss). Over time, these orphaned PVCs may accumulate, silently consuming storage capacity and driving up cloud costs.

Source license: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Publisher excerpt shortened and converted to plain text. Original source license applies.

Read the full original: [Kubernetes](https://kubernetes.io/blog/2026/09/21/kubernetes-v1-37-pvc-last-used-time/)

This record does not reproduce the complete article or represent independent confirmation of every source claim.