Kubernetes has rolled out version 1.31, featuring a crucial enhancement that targets PersistentVolume (PV) leaks during deletion. This update resolves a frequent problem where deleting PersistentVolumeClaims (PVCs) and their associated PersistentVolumes out of order resulted in storage resources remaining in use.
In previous iterations of Kubernetes, if you deleted a bound PV before its PVC, the PV’s reclaim policy would be disregarded, often leaving the underlying storage intact and necessitating manual cleanup. The latest update introduces a beta feature that enforces the reclaim policy, ensuring associated storage is removed from the backend when a PV is deleted.
To take advantage of this feature, follow these steps:
- Upgrade your clusters to Kubernetes version 1.31.
- Utilize the CSI external-provisioner version 5.0.1 or newer.
- Add a finalizer to the PV to prevent its removal from the cluster until the backend storage has been successfully deleted.
This enhancement is particularly useful for users managing dynamic volumes and aligns with the overall objective of improving Kubernetes storage management. However, note that this fix doesn’t apply to statically provisioned in-tree plugin volumes.
These updates reflect Kubernetes’ commitment to refining functionality and enhancing the user experience within cloud-native environments.
For more details, visit the official blog.
