News › linux
By Zayden R., September 1, 2026
Kubernetes v1.37 now enables storage version migration by default, marking its transition to General Availability. This change simplifies the process of updating stored API resource versions, enhancing stability and ease of use for cluster administrators.
Kubernetes has taken a significant step forward with its latest release, v1.37, by enabling storage version migration as a default feature. This enhancement, announced by Google engineer Michael Aspinwall, signifies the migration's graduation to General Availability (GA), promising a more seamless experience for cluster administrators and developers alike.
The core issue addressed by this update is the challenge of managing stale storage versions within Kubernetes. Traditionally, the stored API resources in Kubernetes were written using a specific storage version, which could lead to complications when attempting to update or change these versions. For instance, when a CustomResourceDefinition (CRD) is updated to drop an older API version, such as v1alpha1, administrators could face hurdles if resources are still stored in that outdated version.
Previously, handling these migrations required manual interventions, often involving cumbersome kubectl scripts or deploying external components like kube-storage-version-migrator. These methods were not only labor-intensive but also prone to errors, making the process daunting for many users. With the new built-in StorageVersionMigration API (storagemigration.k8s.io/v1) and the control plane controller now stable and enabled by default, these tasks become significantly more manageable.
The new system simplifies initiating a storage version migration. Administrators can now create a declarative StorageVersionMigration object, which the Kubernetes control plane's StorageVersionMigrator controller automatically processes. This ensures that existing resources are efficiently migrated to the desired storage version without the need for manual oversight.
This update is particularly beneficial in scenarios involving encryption at rest or key rotation, where resources need to be rewritten to reflect new encryption keys. With v1.37, Kubernetes ensures that these critical updates happen smoothly, reducing the risk of unencrypted data lingering in storage.
Overall, enabling storage version migration by default in Kubernetes v1.37 is a solid improvement that alleviates some of the manual burdens previously shouldered by administrators. It's a change that promises to enhance both the stability and security of Kubernetes clusters moving forward.