From 2aefbf760412698a11bbf61676a4ee568ac0b180 Mon Sep 17 00:00:00 2001 From: Ted Avery Date: Wed, 22 Oct 2025 15:18:54 -0400 Subject: [PATCH] OSDOCS-11954:Update storage migration chapter --- _topic_maps/_topic_map_ms.yml | 4 ++-- .../microshift-storage-migration.adoc | 2 +- ...ating-stored-data-to-latest-storage-version.adoc} | 12 ++++++------ 3 files changed, 9 insertions(+), 9 deletions(-) rename {microshift_storage => microshift_updating}/microshift-storage-migration.adoc (87%) rename modules/{microshift-making-storage-migration-request.adoc => microshift-updating-stored-data-to-latest-storage-version.adoc} (81%) diff --git a/_topic_maps/_topic_map_ms.yml b/_topic_maps/_topic_map_ms.yml index 1d28a2e08a..8b7748c008 100644 --- a/_topic_maps/_topic_map_ms.yml +++ b/_topic_maps/_topic_map_ms.yml @@ -112,6 +112,8 @@ Topics: File: microshift-update-rhel-edge-to-image-mode - Name: Listing update package contents File: microshift-list-update-contents +- Name: Updating existing Kubernetes storage objects + File: microshift-storage-migration --- Name: Configuring Dir: microshift_configuring @@ -207,8 +209,6 @@ Topics: File: expanding-persistent-volumes-microshift - Name: Working with volume snapshots File: volume-snapshots-microshift -- Name: Understanding storage migration - File: microshift-storage-migration --- Name: Using AI models Dir: microshift_ai diff --git a/microshift_storage/microshift-storage-migration.adoc b/microshift_updating/microshift-storage-migration.adoc similarity index 87% rename from microshift_storage/microshift-storage-migration.adoc rename to microshift_updating/microshift-storage-migration.adoc index e8c3d983d5..732dc64445 100644 --- a/microshift_storage/microshift-storage-migration.adoc +++ b/microshift_updating/microshift-storage-migration.adoc @@ -8,4 +8,4 @@ toc::[] Storage version migration is used to update existing objects in the {microshift-short} node from their current version to the latest version. The Kube Storage Version Migrator embedded controller is used in {microshift-short} 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. -include::modules/microshift-making-storage-migration-request.adoc[leveloffset=+1] +include::modules/microshift-updating-stored-data-to-latest-storage-version.adoc[leveloffset=+1] diff --git a/modules/microshift-making-storage-migration-request.adoc b/modules/microshift-updating-stored-data-to-latest-storage-version.adoc similarity index 81% rename from modules/microshift-making-storage-migration-request.adoc rename to modules/microshift-updating-stored-data-to-latest-storage-version.adoc index 66b402f446..0feaccfdc1 100644 --- a/modules/microshift-making-storage-migration-request.adoc +++ b/modules/microshift-updating-stored-data-to-latest-storage-version.adoc @@ -1,9 +1,9 @@ // Module included in the following assemblies: // -// * microshift_storage/microshift-storage-migration.adoc +// * microshift_updating/microshift-storage-migration.adoc :_mod-docs-content-type: PROCEDURE -[id="microshift-making-storage-migration-request_{context}"] +[id="microshift-updating-stored-data-to-latest-storage-version_{context}"] = 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. @@ -19,12 +19,12 @@ Updating stored data to the latest Kubernetes storage version is called storage apiVersion: migration.k8s.io/v1alpha1 kind: StorageVersionMigration metadata: - name: snapshot-v1 + name: v1beta1 spec: resource: - group: snapshot.storage.k8s.io - resource: volumesnapshotclasses <1> - version: v1 <2> + group: example.storage.k8s.io + resource: volumeclasses <1> + version: v1alpha1 <2> ---- <1> You must use the plural name of the resource. <2> Version being updated to.