You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/aks/csi-disk-move-subscriptions.md
+12-7Lines changed: 12 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: Move Azure Disk persistent volumes in Azure Kubernetes Service (AKS)
2
+
title: Move Azure Disk persistent volumes to another AKS cluster in the same or a different subscription
3
3
titleSuffix: Azure Kubernetes Service
4
4
description: Learn how to move a persistent volume between Azure Kubernetes Service clusters in the same subscription or a different subscription.
5
5
author: tamram
@@ -9,7 +9,7 @@ ms.topic: article
9
9
ms.date: 04/08/2024
10
10
---
11
11
12
-
# Move Azure Disk persistent volumes to same or different subscription
12
+
# Move Azure Disk persistent volumes to another AKS cluster in the same or a different subscription
13
13
14
14
This article describes how to safely move Azure Disk persistent volumes from one Azure Kubernetes Service (AKS) cluster to another in the same subscription or in a different subscription. The target subscription must be in the same region.
15
15
@@ -69,7 +69,7 @@ It's important to avoid risk of data corruption, inconsistencies, or data loss w
69
69
> [!NOTE]
70
70
> Note the value of the `resourceGroup` field for each disk that you want to move from the output above. This resource group is the node resource group, not the cluster resource group. You'll need the name of this resource group in order to move the disks.
71
71
72
-
1. If `diskState` shows `Attached`, first verify if any workloads are still accessing the volume and stop them first. After a period of time, disk state returns state `Unattached` and can then be moved.
72
+
1. If `diskState` shows `Attached`, first determine whether any workloads are still accessing the volume and stop them. After a period of time, disk state returns state `Unattached` and can then be moved.
73
73
74
74
## Move the persistent volume
75
75
@@ -86,10 +86,10 @@ During this process, you reference:
86
86
87
87
## Verify that the disk volume has been moved
88
88
89
-
After moving the disk volume to the target cluster resource group, validate the resource in the resource group list using the [`az disk list`][az-disk-list] command. Reference the destination resource group where the resources were moved. In this example, the disks were moved to a resource group named *MC_myResourceGroup_myAKSCluster_westus*.
89
+
After moving the disk volume to the target cluster resource group, validate the resource in the resource group list using the [`az disk list`][az-disk-list] command. Reference the destination resource group where the resources were moved. In this example, the disks were moved to a resource group named *MC_myResourceGroup_myAKSCluster_eastus*.
90
90
91
91
```azurecli-interactive
92
-
az disk list --resource-group MC_myResourceGroup_myAKSCluster_westus
92
+
az disk list --resource-group MC_myResourceGroup_myAKSCluster_eastus
93
93
```
94
94
95
95
## Mount the moved disk as a volume
@@ -130,7 +130,7 @@ To mount the moved disk volume, create a static persistent volume with the resou
130
130
- ReadWriteOnce
131
131
resources:
132
132
requests:
133
-
storage: 20Gi
133
+
storage: 10Gi
134
134
volumeName: pv-azuredisk
135
135
storageClassName: managed-csi
136
136
```
@@ -218,18 +218,23 @@ To mount the moved disk volume, create a static persistent volume with the resou
218
218
219
219
## Next steps
220
220
221
+
* For more information about disk-based storage solutions, see [Disk-based solutions in AKS][disk-based-solutions].
222
+
* For more information about storage best practices, see [Best practices for storage and backups in Azure Kubernetes Service][operator-best-practices-storage].
0 commit comments