feat(k8s): tuto

Author: bene2k1

tutorials/migrate-k8s-persistent-volumes-to-multi-az/index.mdx

@@ -3,7 +3,7 @@ meta:
   title: Migrating persistent volumes in a multi-zone Scaleway Kapsule cluster
   description: This tutorial provides information about how to migrate existing Persistent Volumes in a Scaleway Kapsule multi-zone cluster to enhance availability and fault tolerance.
 content:
-  h1: Migrating persistent volumes in a multi-zone Scaleway Kapsul cluster
+  h1: Migrating persistent volumes in a multi-zone Scaleway Kapsule cluster
   paragraph: This tutorial provides information about how to migrate existing Persistent Volumes in a Scaleway Kapsule multi-zone cluster to enhance availability and fault tolerance.
 tags: kapsule elastic-metal migration persistent-volumes
 categories:
@@ -29,7 +29,7 @@ This tutorial provides a generalized approach to migrating Persistent Volumes (P
 
 <Message type="important">
     **Backing up your data is crucial before making any changes.**  
-    Ensure you have a backup strategy in place. You can use tools like Velero for Kubernetes backups or manually copy data to another storage solution. Always verify the integrity of your backups before proceeding.
+    Ensure you have a backup strategy in place. You can use tools like [Velero](/tutorials/k8s-velero-backup/) for Kubernetes backups or manually copy data to another storage solution. Always verify the integrity of your backups before proceeding.
 </Message>
 
 ## Identify existing Persistent Volumes
@@ -50,6 +50,13 @@ This tutorial provides a generalized approach to migrating Persistent Volumes (P
     scw instance volume list
     ```
 
+3. To find the `VOLUME_ID` associated with a PV, correlate it with the output of the following command:
+
+    ```sh
+    scw instance volume list
+    ```
+    Match the PV's details with the corresponding volume in the Scaleway Instance list to identify the correct `VOLUME_ID`.
+
 ## Create snapshots of your existing Persistent Volumes
 
 Use the Scaleway CLI to create snapshots of your volumes.
@@ -91,12 +98,17 @@ Repeat this for each zone required.
 
 Modify your `PersistentVolumeClaims` to reference the newly created volumes.
 
-1. Delete the existing PVC (PVCs are immutable and cannot be updated directly):
+1. Before deleting the existing PVC, scale down your application to prevent data loss:
+    ```sh
+    kubectl scale statefulset my-app --replicas=0
+    ```
+
+2. Delete the existing PVC (PVCs are immutable and cannot be updated directly):
     ```sh
     kubectl delete pvc my-app-pvc
     ```
 
-2. Create a new PVC with a multi-zone compatible `StorageClass`:
+3. Create a new PVC with a multi-zone compatible `StorageClass`:
     ```yaml
     apiVersion: v1
     kind: PersistentVolumeClaim
@@ -111,15 +123,15 @@ Modify your `PersistentVolumeClaims` to reference the newly created volumes.
           storage: 10Gi
     ```
 
-3. Apply the updated PVCs:
+4. Apply the updated PVCs:
     ```sh
     kubectl apply -f my-app-pvc.yaml
     ```
 
 ## Reconfigure the StatefulSet to use multi-zone volumes
 
 1. Edit the `StatefulSet` definition to use the newly created Persistent Volume Claims.
-    Example `StatefulSet` configuration:
+    Example configuration:
 
     ```yaml
     apiVersion: apps/v1