Skip to content

doc: update inline volume doc #1590

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 10, 2024
Merged

doc: update inline volume doc #1590

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion deploy/example/e2e_usage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -133,7 +133,8 @@ In the above example, there is a `/mnt/blob` directory mounted as `blobfuse` fil

#### Option#3: Inline volume
> - inline volume does not support nfs protocol
> - to avoid performance issue, use persistent volume instead of inline volume when numerous pods are accessing the same volume.
> - to avoid performance issue, use persistent volume instead of inline volume when numerous pods are accessing the same volume
> - `secretNamespace` parameter is not required since the secret must be in the same namespace as pod
- 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
Expand Down