Kubernetes v1.37: Storage Version Migration Enabled by Default
AI Summary
Kubernetes v1.37 introduces General Availability for Storage Version Migration (SVM), enabling the built-in StorageVersionMigration API and control plane controller by default. This feature addresses the challenge of stale storage versions in etcd, which occur when Custom Resource Definitions (CRDs) drop older API versions or when encryption keys are rotated. Previously, administrators relied on manual scripts or the out-of-tree kube-storage-version-migrator component. Now, users can declaratively migrate stored resources to the latest default storage version using standard Kubernetes manifests.
Key Takeaways
- StorageVersionMigration API (storagemigration.k8s.io/v1) is now stable and enabled by default in Kubernetes v1.37.
- The feature automatically re-writes resources to the default storage version, aiding in CRD API version deprecation and encryption at rest key rotation.
- Migration progress can be monitored declaratively via kubectl by checking the Succeeded condition on the StorageVersionMigration object status.
Why it matters
Before this GA feature, updating a CRD's storage version or rotating encryption keys required complex, manual, or out-of-tree re-write scripts to ensure legacy unencrypted or outdated schema versions were removed from storage. Having a native, built-in control plane controller simplifies cluster maintenance, secures data at rest migrations, and enables safe deprecation of old API versions.
Conversation 0
Be the first to share your perspective.