|
2 | 2 | title: Use Azure AD in Azure Kubernetes Service
|
3 | 3 | description: Learn how to use Azure AD in Azure Kubernetes Service (AKS)
|
4 | 4 | ms.topic: article
|
5 |
| -ms.date: 04/14/2023 |
| 5 | +ms.date: 04/17/2023 |
6 | 6 | ms.custom: devx-track-azurecli
|
7 | 7 | ms.author: miwithro
|
8 | 8 | ---
|
@@ -144,17 +144,17 @@ In order to access the cluster, follow the steps in [access an Azure AD enabled
|
144 | 144 |
|
145 | 145 | There are some non-interactive scenarios, such as continuous integration pipelines, that aren't currently available with `kubectl`. You can use [`kubelogin`](https://github.com/Azure/kubelogin) to connect to the cluster with a non-interactive service principal credential.
|
146 | 146 |
|
147 |
| -Starting with Kubernetes 1.24, the default format of clusterUser credential for AAD enabled clusters will be ‘exec’, which requires [kubelogin](https://github.com/Azure/kubelogin) binary in the execution PATH. If you are using Azure CLI, it will prompt users to download kubelogin. There will be no behavior change for non-AAD clusters, or AAD clusters whose version is older than 1.24. Existing downloaded kubeconfig will still work. |
| 147 | +Starting with Kubernetes 1.24, the default format of clusterUser credential for AAD enabled clusters will be `exec`, which requires [kubelogin](https://github.com/Azure/kubelogin) binary in the execution PATH. If you are using Azure CLI, it will prompt users to download kubelogin. There will be no behavior change for non-AAD clusters, or AAD clusters whose version is older than 1.24. Existing downloaded kubeconfig will still work. |
148 | 148 |
|
149 |
| -We provide an optional query parameter ‘format’ when getting clusterUser credential to overwrite the default behavior change, you can explicitly specify format to ‘azure’ to get old format kubeconfig. |
| 149 | +We provide an optional query parameter `format` when getting clusterUser credential to overwrite the default behavior change, you can explicitly specify format to `azure` to get old format kubeconfig. |
150 | 150 |
|
151 | 151 | Example:
|
152 | 152 |
|
153 | 153 | ```azurecli-interactive
|
154 | 154 | az aks get-credentials --format azure
|
155 | 155 | ```
|
156 | 156 |
|
157 |
| -For AAD clusters whose version is newer than 1.24, it will return to kubelogin format automatically and no convert needed. For AAD clusters whose version is plder than 1.24, you need to run the below commands to convert kubelogin format manually. |
| 157 | +For AAD clusters whose version is newer than 1.24, it will return to kubelogin format automatically and no conversion needed. For AAD clusters whose version is older than 1.24, you need to run the below commands to convert kube config format manually. |
158 | 158 |
|
159 | 159 | ```azurecli-interactive
|
160 | 160 | export KUBECONFIG=/path/to/kubeconfig
|
@@ -372,7 +372,6 @@ Error from server (Forbidden): nodes is forbidden: User "aaaa11111-11aa-aa11-a1a
|
372 | 372 |
|
373 | 373 | Make sure the admin of the security group has given your account an *Active* assignment.
|
374 | 374 |
|
375 |
| - |
376 | 375 | ## Next steps
|
377 | 376 |
|
378 | 377 | * Learn about [Azure RBAC integration for Kubernetes Authorization][azure-rbac-integration].
|
|
0 commit comments