Ce contenu n'est pas disponible dans la langue sélectionnée.
Chapter 8. Updating existing Kubernetes storage objects
To update existing objects to their latest version without recreating them, use storage version migration in MicroShift. By creating a StorageVersionMigration custom resource (CR), you request the Kube Storage Version Migrator embedded controller to handle the transition automatically.
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 Copier lienLien copié sur presse-papiers!
To update stored data to the latest Kubernetes storage version, perform a storage migration.
The procedure shows an example of converting existing objects on the v1beta1 version to the current version, such as v1beta2, to ensure compatibility with the cluster APIs.
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
Copy to Clipboard Copied! Toggle word wrap Toggle overflow where:
resource.resource- Specifies the plural name of the resource.
resource.version- Specifies the version to update to.
Verification
-
To monitor the progress of the update, review the status of the
StorageVersionMigrationcustom resource (CR).
A migration fails when you misname a group or resource. Incompatible versions between the previous and latest versions can also cause a migration to fail.