@@ -17,7 +17,7 @@ You can also use a different managed-identity for different persistent volumes (
17
17
18
18
- Create a storage account container, e.g.
19
19
``` bash
20
- resourcegroup=" aks-fuseblob -mi"
20
+ resourcegroup=" blobfuse -mi"
21
21
storageaccountname=" myaksblob"
22
22
az storage account create -g " $resourcegroup " -n " $storageaccountname " --access-tier Hot --sku Standard_LRS
23
23
az storage container create -n mycontainer --account-name " $storageaccountname " --public-access off
@@ -28,14 +28,14 @@ You can also use a different managed-identity for different persistent volumes (
28
28
1. Give kubelet identity access to storage account
29
29
` ` ` bash
30
30
aksnprg=" $( az aks list -g " $resourcegroup " --query " [?name == '$aksname '].nodeResourceGroup" -o tsv) "
31
- kloid=" $( az identity list -g " $aksnprg " --query " [?name == 'aks-fuseblob -mi-agentpool'].principalId" -o tsv) "
31
+ kloid=" $( az identity list -g " $aksnprg " --query " [?name == 'blobfuse -mi-agentpool'].principalId" -o tsv) "
32
32
said=" $( az storage account list -g " $resourcegroup " --query " [?name == '$storageaccountname '].id" -o tsv) "
33
33
az role assignment create --assignee-object-id " $kloid " --role " Storage Blob Data Owner" --scope " $said "
34
34
` ` `
35
35
36
36
1. Get the clientID of kubelet identity
37
37
` ` ` bash
38
- az identity list -g " $resourcegroup " --query " [?name == 'aks-fuseblob -mi-agentpool'].clientId" -o tsv
38
+ az identity list -g " $resourcegroup " --query " [?name == 'blobfuse -mi-agentpool'].clientId" -o tsv
39
39
` ` `
40
40
41
41
# # Option#2: grant a dedicated user-assigned managed identity access to storage account
@@ -89,7 +89,7 @@ You can use a dedicated user-assigned managed identity to mount the storage.
89
89
volumeHandle: pv-blob1
90
90
volumeAttributes:
91
91
protocol: fuse
92
- resourceGroup: aks-fuseblob -mi
92
+ resourceGroup: blobfuse -mi
93
93
storageAccount: myaksblob
94
94
containerName: mycontainer
95
95
AzureStorageAuthType: MSI
@@ -252,7 +252,7 @@ You can use a dedicated user-assigned managed identity to mount the storage.
252
252
volumeHandle: pv-blob2
253
253
volumeAttributes:
254
254
protocol: fuse
255
- resourceGroup: aks-fuseblob -mi
255
+ resourceGroup: blobfuse -mi
256
256
storageAccount: myaksblob
257
257
containerName: mycontainer
258
258
AzureStorageAuthType: MSI
0 commit comments