Kubernetes Blog
Follow
Kubernetes v1.33: Prevent PersistentVolume Leaks When Deleting out of Order graduates to GA
Kubernetes v1.33 has graduated a feature to prevent PersistentVolume (PV) leaks when deleting out of order to General Availability (GA). This feature ensures that storage resources are properly reclaimed, preventing unwanted leaks. In previous Kubernetes releases, deleting a PV before its bound PVC would prevent the reclaim policy from being honored. This led to the associated storage asset in the external infrastructure not being removed. With Kubernetes v1.33, this issue is now resolved, and the configured Delete reclaim policy is reliably honored even when PVs are deleted before their bound PVCs. This is achieved through the use of finalizers, ensuring that the storage backend releases the allocated storage resource as intended. For CSI volumes, a finalizer is added to new and existing PVs, which is only removed after the storage from the backend is deleted. The feature does not apply to statically provisioned in-tree plugin volumes. To take advantage of the new behavior, users must upgrade their cluster to Kubernetes v1.33 and run the CSI external-provisioner version 5.0.1 or later. The Kubernetes Storage Special Interest Group (SIG) welcomes new contributors to get involved with the design and development of CSI or any part of the Kubernetes Storage system.