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: deploy/example/e2e_usage.md
+2-4
Original file line number
Diff line number
Diff line change
@@ -101,10 +101,8 @@ Filesystem Size
101
101
In the above example, there is a `/mnt/azurefile` directory mounted as cifs filesystem.
102
102
103
103
#### Option#3: Inline volume
104
-
> only available from `v1.3.0` for SMB protocol (NFS protocol is not supported) <br>
105
-
> inline volume feature can only read storage account name and key in the same namespace, cannot use cluster identity to read storage account name and key <br>
106
-
- Create `azure-secret` with existing storage account name and key in the same namespace as pod
107
-
> in below example, both secret and pod are in `default` namespace
104
+
> to avoid performance issue, use persistent volume instead of inline volume when numerous pods are accessing the same volume.
105
+
- in below SMB protocol example, create `azure-secret` with existing storage account name and key in the same namespace as pod, both secret and pod are in `default` namespace
0 commit comments