Skip to content

Commit e7f851c

Browse files
committed
add add-on info and cluster create info
1 parent 4cb214f commit e7f851c

File tree

1 file changed

+10
-1
lines changed

1 file changed

+10
-1
lines changed

articles/aks/use-managed-identity.md

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ AKS creates two managed identities:
2020
- **System-assigned managed identity**: The identity that the Kubernetes cloud provider uses to create Azure resources on behalf of the user. The life cycle of the system-assigned identity is tied to that of the cluster. The identity is deleted when the cluster is deleted.
2121
- **User-assigned managed identity**: The identity that's used for authorization in the cluster. For example, the user-assigned identity is used to authorize AKS to use access control records (ACRs), or to authorize the kubelet to get metadata from Azure.
2222

23-
Any add-ons also authenticate using a managed identity created by the service.
23+
Add-ons also authenticate using a managed identity. For each add-on, a managed identity is created by AKS and lasts for the life of the add-on.
2424

2525
## Before you begin
2626

@@ -45,6 +45,15 @@ Then, create an AKS cluster:
4545
az aks create -g MyResourceGroup -n MyManagedCluster --enable-managed-identity
4646
```
4747

48+
A successful cluster creation using managed identities contains this service principal profile information:
49+
50+
```json
51+
"servicePrincipalProfile": {
52+
"clientId": "msi",
53+
"secret": null
54+
}
55+
```
56+
4857
Finally, get credentials to access the cluster:
4958

5059
```azurecli-interactive

0 commit comments

Comments
 (0)