With Kubernetes v1.37, storage version migration (SVM) graduates to general availability. This built-in mechanism automatically migrates stored API resources to their designated latest storage schema versions, reducing operational overhead and risks tied to stale resource versions.
- Automated storage version migration enabled by default for all clusters
- Simplifies CRD version deprecation and encryption key rotation processes
- Improves observability with declarative migration status tracking
Infrastructure signal
Kubernetes v1.37 introduces StorageVersionMigration as a stable core feature enabled by default across all clusters running this version. This marks a crucial shift in how stored API resources are managed at the control plane level, eliminating the need for external migrator components or manual scripting.
The built-in migration controller monitors declarative StorageVersionMigration objects and efficiently rewrites stored resources to align with the latest storage version designated for each API. This control plane enhancement reduces the risk of inconsistent storage versions that can complicate upgrades, data encryption, and key rotation tasks.
Developer impact
For developers and cluster operators, the default activation of storage version migration removes prior complexities associated with promoting new API versions or retiring old ones. It ensures that resources are serially stored using the current schema, avoiding data retention in deprecated formats that could pose compatibility or security challenges.
The mechanism supports more declarative workflows by allowing migration processes to be bundled directly with CustomResourceDefinition manifests. Status conditions on migration objects provide clear observability into migration progress, improving confidence and self-service diagnostics during upgrades or encryption updates.
What teams should watch
Teams managing Kubernetes CRDs and sensitive workloads with encryption-at-rest enabled should prioritize adopting and integrating the new StorageVersionMigration capabilities. Particularly, this ensures the timely and safe deprecation of obsolete API storage versions and facilitates encryption key rotation compliance by rewriting existing stored resources.
Observability teams can leverage migration status tracking for automated monitoring and alerts around storage version health. Additionally, teams should monitor for any in-flight CRD updates during migration attempts, as these may necessitate retrying migrations to fully stabilize API resource storage versions.