From e2fe28fa6e863c7a640ec62ddc7a24c0aff57715 Mon Sep 17 00:00:00 2001 From: andyzhangx Date: Sat, 7 Oct 2023 07:42:31 +0000 Subject: [PATCH] doc: refine inline volume example fix --- deploy/example/e2e_usage.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/deploy/example/e2e_usage.md b/deploy/example/e2e_usage.md index 29eec56aff..5ac43b14e1 100644 --- a/deploy/example/e2e_usage.md +++ b/deploy/example/e2e_usage.md @@ -134,9 +134,8 @@ blobfuse 14G 41M 13G 1% /mnt/blob In the above example, there is a `/mnt/blob` directory mounted as `blobfuse` filesystem. #### Option#3: Inline volume - > only available from `v1.2.0` for blobfuse protocol (NFS protocol is not supported) - - Create `azure-secret` with existing storage account name and key in the same namespace as pod - > in below example, both secret and pod are in `default` namespace + > to avoid performance issue, use persistent volume instead of inline volume when numerous pods are accessing the same volume. + > in below blobfuse mount 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 ```console kubectl create secret generic azure-secret --from-literal azurestorageaccountname=NAME --from-literal azurestorageaccountkey="KEY" --type=Opaque ```