You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
## option#1: grant kubelet identity access to storage account
33
27
34
28
1. Give kubelet identity access to storage account
35
29
```bash
@@ -44,7 +38,7 @@ You can also use a different managed-identity for different persistent volumes (
44
38
az identity list -g "$resourcegroup" --query "[?name == 'aks-fuseblob-mi-agentpool'].clientId" -o tsv
45
39
```
46
40
47
-
## Using a dedicated user-assigned managed identity
41
+
## option#2: grant a dedicated user-assigned managed identity access to storage account
48
42
You can use a dedicated user-assigned managed identity to mount the storage.
49
43
50
44
1. Create user-assigned managed identity and give access to storage account
@@ -150,22 +144,6 @@ You can use a dedicated user-assigned managed identity to mount the storage.
150
144
persistentVolumeClaim:
151
145
claimName: pvc-blob1
152
146
status: {}
153
-
154
-
---
155
-
156
-
apiVersion: v1
157
-
kind: Service
158
-
metadata:
159
-
name: nginx-app1
160
-
labels:
161
-
run: nginx-app1
162
-
spec:
163
-
ports:
164
-
- port: 80
165
-
protocol: TCP
166
-
selector:
167
-
app: nginx-app1
168
-
type: LoadBalancer
169
147
```
170
148
171
149
1. Apply the yaml files
@@ -262,10 +240,3 @@ You can use a dedicated user-assigned managed identity to mount the storage.
262
240
```
263
241
264
242
1. Now you can use the persistent volume claim ``pv-blob2``in another deployment.
265
-
266
-
# Security consideration
267
-
You should use at least 2 nodepools (a system and a user node pool) and assign the storage identities just to the user nodepool. Identity needs to be assigned where the pvs are mounted.
268
-
You can use tains to protect the user assigned identity to schedule only authorized pods on the nodepool, that requires the pvs.
0 commit comments