Merge pull request #100965 from tedaveryredhat/OSDOCS-11954

OSDOCS-11954:Update storage migration chapter

Author: mburke5678

_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

…torage/microshift-storage-migration.adoc …dating/microshift-storage-migration.adocmicroshift_storage/microshift-storage-migration.adoc renamed to microshift_updating/microshift-storage-migration.adoc microshift_storage/microshift-storage-migration.adoc renamed to 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]

…ft-making-storage-migration-request.adoc …ored-data-to-latest-storage-version.adocmodules/microshift-making-storage-migration-request.adoc renamed to modules/microshift-updating-stored-data-to-latest-storage-version.adoc modules/microshift-making-storage-migration-request.adoc renamed to 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.