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/manage-azure-rbac.md
+23-13Lines changed: 23 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -103,6 +103,13 @@ az role assignment create --role "Azure Kubernetes Service RBAC Admin" --assigne
103
103
> az role assignment create --role "Azure Kubernetes Service RBAC Reader" --assignee <AAD-ENTITY-ID> --scope $AKS_ID/namespaces/<namespace-name>
104
104
> ```
105
105
106
+
> [!NOTE]
107
+
> In Azure portal, after creating role assignments scoped to a desired namespace, you won't be able to see "role assignments" for namespace [at a scope][list-role-assignments-at-a-scope-at-portal]. You can find it by using the [`az role assignment list`][az-role-assignment-list] command, or [list role assignments for a user or group][list-role-assignments-for-a-user-or-group-at-portal], which you assigned the role to.
108
+
>
109
+
> ```azurecli-interactive
110
+
> az role assignment list --scope $AKS_ID/namespaces/<namespace-name>
111
+
> ```
112
+
106
113
## Create custom roles definitions
107
114
108
115
The following example custom role definition allows a user to only read deployments and nothing else. For the full list of possible actions, see [Microsoft.ContainerService operations](../role-based-access-control/resource-provider-operations.md#microsoftcontainerservice).
@@ -215,19 +222,22 @@ To learn more about AKS authentication, authorization, Kubernetes RBAC, and Azur
0 commit comments