Skip to content

Commit 5142c8f

Browse files
Merge pull request #16181 from leslielin-5/patch-19
Update aks-create-clusters-cli.md
2 parents 4514ac3 + 39081ec commit 5142c8f

File tree

1 file changed

+2
-4
lines changed

1 file changed

+2
-4
lines changed

AKS-Hybrid/aks-create-clusters-cli.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -52,10 +52,8 @@ az aksarc create -n $aksclustername -g $resource_group --custom-location $custom
5252

5353
After a few minutes, the command completes and returns JSON-formatted information about the cluster.
5454

55-
> [!NOTE]
56-
> - The SSH key value is the public key for accessing nodes in the provisioned cluster. By default, this key is located at `~/.ssh/id_rsa.pub`. You can specify a different location using the `--ssh-key-value` parameter during cluster creation.
57-
> - The `--generate-ssh-keys` parameter is required if there's no pre-existing SSH key on your local machine. If you don't include this parameter during cluster creation and no SSH key exists, you receive an error message.
58-
> - If you already have an SSH key on your local machine, the AKS cluster reuses that key. In this case, specifying `--generate-ssh-keys`, or omitting that parameter, has no effect.
55+
[!NOTE]
56+
To use Azure RBAC or workload identity for an AKS cluster, you must pass the required parameters during cluster creation using Azure CLI. Currently, updating an existing AKS cluster to enable workload identity and/or Azure RBAC is not supported. For more information, see [Use Azure RBAC for Kubernetes authorization](/azure/aks/hybrid/azure-rbac-23h2) or [Deploy and configure Workload Identity for your cluster}(workload-identity.md).
5957

6058
## Connect to the Kubernetes cluster
6159

0 commit comments

Comments
 (0)