Skip to content

Commit a11964d

Browse files
authored
Update README.md
1 parent 29a2870 commit a11964d

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

deploy/example/cloning/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@
88
- 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
99
- if the driver controller pod is managed by AKS, you need to set `Enable from all networks` in the storage account's VNet settings
1010
- Before proceeding, ensure that the application is not writing data to the source volume.
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.
11+
- ensure that you have granted the `Storage File Data Privileged Contributor` role to the CSI driver controller identity; otherwise, the driver will utilize an SAS key for volume cloning operations.
1212

1313
## Create a Source PVC
1414

0 commit comments

Comments
 (0)