• Kubernetes v1.35: Mutable PersistentVolume Node Affinity (alpha) The PersistentVolume node affinity API dates back to Kubernetes v1.10. • It is widely used to express that volumes may not be equally accessible by all nodes in the cluster. • This field was previously immutable, and it is now mutable in Kubernetes v1.35 (alpha). • This change opens a door to more flexible online volume management. • Why make node affinity mutable? • This raises an obvious question: why make node affinity mutable now?

Article Summaries:

  • Kubernetes v1.35 introduces the Mutable PersistentVolume Node Affinity feature (alpha). Previously, a PV’s nodeAffinity field was immutable, limiting the ability to adapt to changes in storage provider capabilities such as migrating from zonal to regional disks or upgrading to newer disk generations. By enabling the MutablePVNodeAffinity feature gate, cluster administrators can edit a PV’s nodeAffinity to reflect new topology constraints, allowing Pods to be scheduled on appropriate nodes without data loss. The change is currently alpha, disabled by default, and requires proper RBAC permissions. It marks a first step toward more flexible online volume management, though further ecosystem integration is needed.

Sources: