You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/aks/control-kubeconfig-access.md
+13-9Lines changed: 13 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,13 +27,13 @@ There are two Azure roles you can apply to an Azure Active Directory (Azure AD)
27
27
28
28
1.**Azure Kubernetes Service Cluster Admin Role**
29
29
30
-
* Allows access to *Microsoft.ContainerService/managedClusters/listClusterAdminCredential/action* API call. This API call [lists the cluster admin credentials][api-cluster-admin].
31
-
* Downloads *kubeconfig* for the *clusterAdmin* role.
30
+
* Allows access to `Microsoft.ContainerService/managedClusters/listClusterAdminCredential/action` API call. This API call [lists the cluster admin credentials][api-cluster-admin].
31
+
* Downloads *kubeconfig* for the *clusterAdmin* role.
32
32
33
33
2.**Azure Kubernetes Service Cluster User Role**
34
34
35
-
* Allows access to *Microsoft.ContainerService/managedClusters/listClusterUserCredential/action* API call. This API call [lists the cluster user credentials][api-cluster-user].
36
-
* Downloads *kubeconfig* for *clusterUser* role.
35
+
* Allows access to `Microsoft.ContainerService/managedClusters/listClusterUserCredential/action` API call. This API call [lists the cluster user credentials][api-cluster-user].
36
+
* Downloads *kubeconfig* for *clusterUser* role.
37
37
38
38
> [!NOTE]
39
39
> On clusters that use Azure AD, users with the *clusterUser* role have an empty *kubeconfig* file that prompts a login. Once logged in, users have access based on their Azure AD user or group settings. Users with the *clusterAdmin* role have admin access.
@@ -42,11 +42,11 @@ There are two Azure roles you can apply to an Azure Active Directory (Azure AD)
42
42
43
43
## Assign role permissions to a user or group
44
44
45
-
To assign one of the available roles, you need to get the resource ID of the AKS cluster and the ID of the Azure AD user account or group using the following commands:
45
+
To assign one of the available roles, you need to get the resource ID of the AKS cluster and the ID of the Azure AD user account or group using the following steps:
46
46
47
-
* Get the cluster resource ID using the [`az aks show`][az-aks-show] command for the cluster named *myAKSCluster* in the *myResourceGroup* resource group. Provide your own cluster and resource group name as needed.
48
-
* Use the [`az account show`][az-account-show] and [`az ad user show`][az-ad-user-show] commands to get your user ID.
49
-
* Assign a role using the [`az role assignment create`][az-role-assignment-create] command.
47
+
1. Get the cluster resource ID using the [`az aks show`][az-aks-show] command for the cluster named *myAKSCluster* in the *myResourceGroup* resource group. Provide your own cluster and resource group name as needed.
48
+
2. Use the [`az account show`][az-account-show] and [`az ad user show`][az-ad-user-show] commands to get your user ID.
49
+
3. Assign a role using the [`az role assignment create`][az-role-assignment-create] command.
50
50
51
51
The following example assigns the *Azure Kubernetes Service Cluster Admin Role* to an individual user account:
52
52
@@ -76,7 +76,7 @@ az ad group show --group appdev --query objectId -o tsv
76
76
> [!IMPORTANT]
77
77
> In some cases, such as Azure AD guest users, the *user.name* in the account is different than the *userPrincipalName*.
0 commit comments