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
@@ -130,14 +133,15 @@ az aks show -g <RGName> -n <ClusterName> --query "identity"
130
133
```
131
134
132
135
> [!NOTE]
133
-
> For creating and using your own VNet, static IP address, or attached Azure disk where the resources are outside of the worker node resource group, use the PrincipalID of the cluster System Assigned Managed Identity to perform a role assignment. For more information on role assignment, see [Delegate access to other Azure resources](kubernetes-service-principal.md#delegate-access-to-other-azure-resources).
136
+
> For creating and using your own VNet, static IP address, or attached Azure disk where the resources are outside of the worker node resource group, CLI will add the role assignement automatically. If you are using ARM template or other clients, you need to use the PrincipalID of the cluster System Assigned Managed Identity to perform a role assignment. For more information on role assignment, see [Delegate access to other Azure resources](kubernetes-service-principal.md#delegate-access-to-other-azure-resources).
134
137
>
135
138
> Permission grants to cluster Managed Identity used by Azure Cloud provider may take up 60 minutes to populate.
136
139
137
140
138
141
## Bring your own control plane MI
139
142
A custom control plane identity enables access to be granted to the existing identity prior to cluster creation. This feature enables scenarios such as using a custom VNET or outboundType of UDR with a pre-created managed identity.
140
143
144
+
141
145
You must have the Azure CLI, version 2.15.1 or later installed.
142
146
143
147
### Limitations
@@ -149,29 +153,9 @@ If you don't have a managed identity yet, you should go ahead and create one for
149
153
az identity create --name myIdentity --resource-group myResourceGroup
150
154
```
151
155
152
-
Assign "Managed Identity Operator" role to the identity.
153
-
156
+
Azure CLI will automatically add required role assignment for control plane MI. If you are using ARM template or other clients, you need to create the role assignment manually.
154
157
```azurecli-interactive
155
-
az role assignment create --assignee <id> --role "Managed Identity Operator" --scope <id>
az role assignment create --assignee <control-plane-identity-object-id> --role "Managed Identity Operator" --scope <kubelet-identity-resource-id>
175
159
```
176
160
177
161
If your managed identity is part of your subscription, you can use [az identity CLI command][az-identity-list] to query it.
@@ -218,6 +202,7 @@ A Kubelet identity enables access to be granted to the existing identity prior t
218
202
> [!WARNING]
219
203
> Updating kubelet MI will upgrade Nodepool, which causes downtime for your AKS cluster as the nodes in the nodepools will be cordoned/drained and then reimaged.
220
204
205
+
221
206
### Prerequisites
222
207
223
208
- You must have the Azure CLI, version 2.26.0 or later installed.
@@ -283,7 +268,7 @@ az identity list --query "[].{Name:name, Id:id, Location:location}" -o table
283
268
284
269
### Create a cluster using kubelet identity
285
270
286
-
Now you can use the following command to create your cluster with your existing identities. Provide the control plane identity id via `assign-identity` and the kubelet managed identity via `assign-kubelet-identity`:
271
+
Now you can use the following command to create your cluster with your existing identities. Provide the control plane identity resource ID via `assign-identity` and the kubelet managed identity via `assign-kubelet-identity`:
A successful cluster creation using your own kubelet managed identity contains the following output:
@@ -337,15 +322,15 @@ az upgrade
337
322
```
338
323
#### Updating your cluster with kubelet identity
339
324
340
-
Now you can use the following command to update your cluster with your existing identities. Provide the control plane identity id via `assign-identity` and the kubelet managed identity via `assign-kubelet-identity`:
325
+
Now you can use the following command to update your cluster with your existing identities. Provide the control plane identity resource ID via `assign-identity` and the kubelet managed identity via `assign-kubelet-identity`:
0 commit comments