Skip to content

Commit 0017dd9

Browse files
authored
Update README.md
1 parent 76ab2b6 commit 0017dd9

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

deploy/example/cloning/README.md

+3-2
Original file line numberDiff line numberDiff line change
@@ -5,9 +5,10 @@
55
- NFSv3 protocol is not supported
66

77
## Prerequisites
8-
- Make sure that the virtual network, where the driver controller pod is deployed, is added to the allowed list of the storage account's VNet setting.
8+
- Make sure that the virtual network hosting the driver controller pod is added to the list of allowed virtual networks in the storage account's VNet settings
9+
- if the driver controller pod is managed by AKS, you need to set `Enable from all networks` in the storage account's VNet settings
910
- Before proceeding, ensure that the application is not writing data to the source volume.
10-
- In order to allow the use of a managed identity, the source storage account requires the `Storage Blob Data Reader` role, while the destination storage account requires the `Storage Blob Data Contributor` role. If the Storage Blob Data role is not granted, the CSI driver will use a SAS token as a fallback.
11+
- In order to allow the use of a managed identity, the source storage account requires the `Storage Blob Data Reader` role, while the destination storage account requires the `Storage Blob Data Contributor` role. If the Storage Blob Data role is not granted, the CSI driver will use SAS token as fallback.
1112

1213
## Create a Source PVC
1314

0 commit comments

Comments
 (0)