Skip to content
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

doc: refine inline volume example #1477

Merged
merged 1 commit into from
Oct 7, 2023
Merged

doc: refine inline volume example #1477

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
6 changes: 2 additions & 4 deletions deploy/example/e2e_usage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -101,10 +101,8 @@ Filesystem Size
In the above example, there is a `/mnt/azurefile` directory mounted as cifs filesystem.

#### Option#3: Inline volume
> only available from `v1.3.0` for SMB protocol (NFS protocol is not supported) <br>
> 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>
- 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 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
```console
kubectl create secret generic azure-secret --from-literal azurestorageaccountname=NAME --from-literal azurestorageaccountkey="KEY" --type=Opaque
```
Expand Down