So... Kubernetes just made persistent storage much safer to manage with the v1.37
retained text
One thing I'm extremely careful with in production is storage. I can recreate a pod. I can redeploy an application. But if I accidentally delete a PVC containing important database files, that's a completely different problem. Until now, when I found an old PVC in my cluster, answering a simple question wasn't always straightforward: **"Is anything still using this?"** I would have to check my pods, PVCs and PersistentVolumes before deciding whether that storage was actually abandoned. It worked... But when I'm dealing with database files and persistent application data, **I don't want to guess.** Kubernetes v1.37 makes this much better with `PersistentVolumeClaimUnusedSinceTime`. Now Kubernetes adds an `Unused` condition directly to the PVC. If a pod is still referencing it: `Unused=False` If no active pod is referencing it: `Unused=True` But this is the part I really like. Kubernetes also gives me `lastTransitionTime`. So I don't only know that a PVC is currently unused. **I can see how long it has been unused.** That gives me much better information before I touch storage containing potentially important application or database data. For example, instead of deleting a PVC simply because I don't see a running pod attached to it, I can build a safer process around it: **Unused → verify → retain for a defined period → backup/archive if necessary → then clean up.** And pending pods still count as using the PVC, which is important because Kubernetes understands that a workload intends to use that storage even if the pod hasn't started running yet. This is the kind of Kubernetes update I like. Not because it's another feature to memorize... But because it helps me make **safer decisions around persistent production data.**
document fetched 2026-09-26 00:37 · canonical https://reddit.com/r/kubernetes/comments/1wq7n0n/so_kubernetes_just_made_persistent_storage_much