|
1 | 1 | ---
|
2 | 2 | title: "Azure RBAC on Azure Arc-enabled Kubernetes clusters"
|
3 |
| -ms.date: 05/22/2024 |
| 3 | +ms.date: 05/28/2024 |
4 | 4 | ms.topic: how-to
|
5 | 5 | ms.custom: devx-track-azurecli
|
6 | 6 | description: "Use Azure RBAC for authorization checks on Azure Arc-enabled Kubernetes clusters."
|
@@ -43,17 +43,16 @@ For a conceptual overview of this feature, see [Azure RBAC on Azure Arc-enabled
|
43 | 43 | az connectedk8s show -g <resource-group> -n <connected-cluster-name>
|
44 | 44 | ```
|
45 | 45 |
|
46 |
| -1. Get the ED (`identity.principalId`) from the output and run the following command to assign the **Connected Cluster Managed Identity CheckAccess Reader** role to the cluster MSI: |
| 46 | +1. Get the ID (`identity.principalId`) from the output and run the following command to assign the **Connected Cluster Managed Identity CheckAccess Reader** role to the cluster MSI: |
47 | 47 |
|
48 | 48 | ```azurecli
|
49 | 49 | az role assignment create --role "Connected Cluster Managed Identity CheckAccess Reader" --assignee "<Cluster MSI ID>" --scope <cluster ARM ID>
|
50 | 50 | ```
|
51 | 51 |
|
52 |
| - |
53 | 52 | 1. Enable Azure role-based access control (RBAC) on your Azure Arc-enabled Kubernetes cluster by running the following command:
|
54 | 53 |
|
55 | 54 | ```azurecli
|
56 |
| - az connectedk8s enable-features -n <clusterName> -g <resourceGroupName> --features azure-rbac --app-id "${SERVER_APP_ID}" --app-secret "${SERVER_APP_SECRET}" |
| 55 | + az connectedk8s enable-features -n <clusterName> -g <resourceGroupName> --features azure-rbac |
57 | 56 | ```
|
58 | 57 |
|
59 | 58 | > [!NOTE]
|
@@ -344,12 +343,12 @@ Using a shared kubeconfig requires slightly different steps depending on your Ku
|
344 | 343 | sudo chmod +x /usr/local/bin/kubelogin
|
345 | 344 | ```
|
346 | 345 |
|
347 |
| -1. [Convert](https://azure.github.io/kubelogin/cli/convert-kubeconfig.html) the kubelogin to use the appropriate [login mode](https://azure.github.io/kubelogin/concepts/login-modes.html). For example, for [device code login](https://azure.github.io/kubelogin/concepts/login-modes/devicecode.html) with a Microsoft Entra user, the commands would be as follows: |
| 346 | +1. [Convert](https://azure.github.io/kubelogin/concepts/azure-arc.html) the kubelogin to use the appropriate [login mode](https://azure.github.io/kubelogin/concepts/login-modes.html). For example, for [device code login](https://azure.github.io/kubelogin/concepts/login-modes/devicecode.html) with a Microsoft Entra user, the commands would be as follows: |
348 | 347 |
|
349 | 348 | ```bash
|
350 | 349 | export KUBECONFIG=/path/to/kubeconfig
|
351 | 350 |
|
352 |
| - kubelogin convert-kubeconfig |
| 351 | + kubelogin convert-kubeconfig --pop-enabled --pop-claims 'u=<ARM ID of cluster>" |
353 | 352 | ```
|
354 | 353 |
|
355 | 354 | ### [Kubernetes < v1.26](#tab/Kubernetes-earlier)
|
|
0 commit comments