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/trusted-access-feature.md
+17-28Lines changed: 17 additions & 28 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,26 +47,28 @@ In the same subscription as the Azure resource that you want to access the clust
47
47
48
48
The roles that you select depend on the Azure services that you want to access the AKS cluster. Azure services help create roles and role bindings that build the connection from the Azure service to AKS.
49
49
50
+
To find the roles that you need, see the documentation for the Azure service that you want to connect to AKS. You can also use the Azure CLI to list the roles that are available for the Azure service. For example, to list the roles for Azure Machine Learning, use the following command:
51
+
52
+
```azurecli-interactive
53
+
az aks trustedaccess role list --location $LOCATION
54
+
```
55
+
50
56
## Create a Trusted Access role binding
51
57
52
58
After you confirm which role to use, use the Azure CLI to create a Trusted Access role binding in the AKS cluster. The role binding associates your selected role with the Azure service.
53
59
54
60
```azurecli
55
61
# Create a Trusted Access role binding in an AKS cluster
56
62
57
-
az aks trustedaccess rolebinding create --resource-group <AKS resource group> --cluster-name <AKS cluster name> -n <role binding name> -s <connected service resource ID> --roles <roleName1, roleName2>
63
+
az aks trustedaccess rolebinding create --resource-group $RESOURCE_GROUP_NAME --cluster-name $CLUSTER_NAME --name $ROLE_BINDING_NAME --source-resource-id $SOURCE_RESOURCE_ID --roles $ROLE_NAME_1,$ROLE_NAME_2
az aks trustedaccess rolebinding create --resource-group myResourceGroup --cluster-name myAKSCluster --name test-binding --source-resource-id /subscriptions/000-000-000-000-000/resourceGroups/myResourceGroup/providers/Microsoft.MachineLearningServices/workspaces/MyMachineLearning --roles Microsoft.MachineLearningServices/workspaces/mlworkload
70
72
```
71
73
72
74
## Update an existing Trusted Access role binding
@@ -76,39 +78,26 @@ For an existing role binding that has an associated source service, you can upda
76
78
> [!NOTE]
77
79
> The add-on manager updates clusters every five minutes, so the new role binding might take up to five minutes to take effect. Before the new role binding takes effect, the existing role binding still works.
78
80
>
79
-
> You can use `az aks trusted access rolebinding list --name <role binding name> --resource-group <resource group>` to check the current role binding.
80
-
81
-
```azurecli
82
-
# Update the RoleBinding command
83
-
84
-
az aks trustedaccess rolebinding update --resource-group <AKS resource group> --cluster-name <AKS cluster name> -n <existing role binding name> --roles <newRoleName1, newRoleName2>
85
-
```
81
+
> You can use the `az aks trusted access rolebinding list` command to check the current role binding.
86
82
87
-
Here's an example:
88
-
89
-
```azurecli
90
-
# Update the RoleBinding command with sample resource group, cluster, and roles
0 commit comments