Skip to content

Commit 9179384

Browse files
authored
Update managed-aad.md
1 parent 1dd33ff commit 9179384

File tree

1 file changed

+4
-5
lines changed

1 file changed

+4
-5
lines changed

articles/aks/managed-aad.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Use Azure AD in Azure Kubernetes Service
33
description: Learn how to use Azure AD in Azure Kubernetes Service (AKS)
44
ms.topic: article
5-
ms.date: 04/14/2023
5+
ms.date: 04/17/2023
66
ms.custom: devx-track-azurecli
77
ms.author: miwithro
88
---
@@ -144,17 +144,17 @@ In order to access the cluster, follow the steps in [access an Azure AD enabled
144144

145145
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.
146146

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.
148148

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.
150150

151151
Example:
152152

153153
```azurecli-interactive
154154
az aks get-credentials --format azure
155155
```
156156

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.
158158

159159
```azurecli-interactive
160160
export KUBECONFIG=/path/to/kubeconfig
@@ -372,7 +372,6 @@ Error from server (Forbidden): nodes is forbidden: User "aaaa11111-11aa-aa11-a1a
372372

373373
Make sure the admin of the security group has given your account an *Active* assignment.
374374

375-
376375
## Next steps
377376

378377
* Learn about [Azure RBAC integration for Kubernetes Authorization][azure-rbac-integration].

0 commit comments

Comments
 (0)