Skip to content

Commit c226b02

Browse files
committed
update static provisoning doc
1 parent e7b3a4c commit c226b02

File tree

4 files changed

+9
-7
lines changed

4 files changed

+9
-7
lines changed

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -49,9 +49,9 @@ kubectl create -f https://raw.githubusercontent.com/csi-driver/blobfuse-csi-driv
4949
### Static Provisioning(use an existing storage account)
5050
#### Option#1: use existing credentials in k8s cluster
5151
> make sure the existing credentials in k8s cluster(e.g. service principal, msi) could access the specified storage account
52-
- Download a blobfuse CSI storage class, edit `resourceGroup`, `storageAccount`, `containerName` to use existing storage container
52+
- Download a blobfuse CSI storage class, edit `resourceGroup`, `storageAccount`, `containerName` in storage class
5353
```sh
54-
wget -O storageclass-blobfuse-csi-existing-container.yaml https://raw.githubusercontent.com/csi-driver/blobfuse-csi-driver/master/deploy/example/storageclass-blobfuse-csi-existing-container.yaml
54+
wget https://raw.githubusercontent.com/csi-driver/blobfuse-csi-driver/master/deploy/example/storageclass-blobfuse-csi-existing-container.yaml
5555
vi storageclass-blobfuse-csi-existing-container.yaml
5656
kubectl create -f storageclass-blobfuse-csi-existing-container.yaml
5757
```
@@ -67,7 +67,7 @@ kubectl create -f https://raw.githubusercontent.com/csi-driver/blobfuse-csi-driv
6767
kubectl create secret generic azure-secret --from-literal accountname=NAME --from-literal accountkey="KEY" --type=Opaque
6868
```
6969

70-
- Create a blobfuse CSI PV, download `pv-blobfuse-csi.yaml` file and edit `containerName` in `volumeAttributes`
70+
- Create a blobfuse CSI PV, download `pv-blobfuse-csi.yaml` file and edit `resourceGroup`, `storageAccount`, `containerName` in `volumeAttributes`
7171
```sh
7272
wget https://raw.githubusercontent.com/csi-driver/blobfuse-csi-driver/master/deploy/example/pv-blobfuse-csi.yaml
7373
vi pv-blobfuse-csi.yaml

deploy/example/pv-blobfuse-csi.yaml

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,13 +7,15 @@ spec:
77
storage: 10Gi
88
accessModes:
99
- ReadWriteMany
10-
persistentVolumeReclaimPolicy: Retain
10+
persistentVolumeReclaimPolicy: Retain #If set as "Delete" container would be removed after pvc deletion
1111
csi:
1212
driver: blobfuse.csi.azure.com
1313
readOnly: false
1414
volumeHandle: arbitrary-volumeid
1515
volumeAttributes:
16-
sharename: k8stest
16+
resourceGroup: EXISTING_RESOURCE_GROUP
17+
storageAccount: EXISTING_STORAGE_ACCOUNT
18+
containerName: EXISTING_CONTAINER_NAME
1719
nodePublishSecretRef:
1820
name: azure-secret
1921
namespace: default

deploy/example/storageclass-blobfuse-csi-existing-container.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,5 +8,5 @@ parameters:
88
resourceGroup: EXISTING_RESOURCE_GROUP
99
storageAccount: EXISTING_STORAGE_ACCOUNT
1010
containerName: EXISTING_CONTAINER_NAME
11-
reclaimPolicy: Retain
11+
reclaimPolicy: Retain #If set as "Delete" container would be removed after pvc deletion
1212
volumeBindingMode: Immediate

deploy/example/storageclass-blobfuse-csi.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,5 +5,5 @@ metadata:
55
provisioner: blobfuse.csi.azure.com
66
parameters:
77
skuName: Standard_LRS #available values: Standard_LRS, Standard_GRS, Standard_RAGRS
8-
reclaimPolicy: Retain
8+
reclaimPolicy: Retain #If set as "Delete" container would be removed after pvc deletion
99
volumeBindingMode: Immediate

0 commit comments

Comments
 (0)