此内容没有您所选择的语言版本。

Chapter 8. Updating existing Kubernetes storage objects


Storage version migration is used to update existing objects in the MicroShift node 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 re-create 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 StorageVersionMigration API 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
    Copy to Clipboard Toggle word wrap

    1
    You must use the plural name of the resource.
    2
    Version being updated to.
  • The progress of the migration is posted to the StorageVersionMigration status.
Note
  • 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.
返回顶部
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务,以及可以信赖的内容,帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

Theme

© 2025 Red Hat