Chapter 8. Updating existing Kubernetes storage objects
Storage version migration is used to update existing objects in the cluster from their current version to the latest version. The Kube Storage Version Migrator embedded controller is used in MicroShift to migrate resources without having to recreate those resources. Either you or a controller can create a StorageVersionMigration custom resource (CR) that requests a migration through the Migrator Controller.
8.1. Updating stored data to the latest storage version
Updating stored data to the latest Kubernetes storage version is called storage migration. For example, updating from v1beta1 to v1beta2 is migration. To update your storage version, use the following procedure.
Procedure
Either you or any controller that has support for the
StorageVersionMigrationAPI must trigger a migration request. Use the following example request for reference:Example request
apiVersion: migration.k8s.io/v1alpha1 kind: StorageVersionMigration metadata: name: snapshot-v1 spec: resource: group: snapshot.storage.k8s.io resource: volumesnapshotclasses 1 version: v1 2-
The progress of the migration is posted to the
StorageVersionMigrationstatus.
- Failures can occur because of a misnamed group or resource.
- Migration failures can also occur when there is an incompatibility between the previous and latest versions.
