Documentation update - solves issue #4132

Adding userAssignedIdentityID of the kubelet identity solves the problem with multiple parallel node pool identities - issue #4132
This commit is contained in:
Thomas Hesse 2023-12-21 22:57:51 +01:00 committed by GitHub
parent 0f5ff5f3aa
commit df122b03fd
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -140,7 +140,8 @@ For the managed identity, the contents of `azure.json` should be similar to this
"tenantId": "01234abc-de56-ff78-abc1-234567890def",
"subscriptionId": "01234abc-de56-ff78-abc1-234567890def",
"resourceGroup": "MyDnsResourceGroup",
"useManagedIdentityExtension": true
"useManagedIdentityExtension": true,
"userAssignedIdentityID": "01234abc-de56-ff78-abc1-234567890def"
}
```
@ -151,6 +152,8 @@ For this process, you will need to get the kubelet identity:
```bash
$ PRINCIPAL_ID=$(az aks show --resource-group $CLUSTER_GROUP --name $CLUSTERNAME \
--query "identityProfile.kubeletidentity.objectId" --output tsv)
$ IDENTITY_CLIENT_ID=$(az aks show --resource-group $CLUSTER_GROUP --name $CLUSTERNAME \
--query "identityProfile.kubeletidentity.clientId" --output tsv)
```
#### Assign rights for the Kubelet identity
@ -178,7 +181,8 @@ cat <<-EOF > /local/path/to/azure.json
"tenantId": "$(az account show --query tenantId -o tsv)",
"subscriptionId": "$(az account show --query id -o tsv)",
"resourceGroup": "$AZURE_DNS_ZONE_RESOURCE_GROUP",
"useManagedIdentityExtension": true
"useManagedIdentityExtension": true,
"userAssignedIdentityID": "$IDENTITY_CLIENT_ID"
}
EOF
```