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
Next, you [update AKS cluster with new service principal credentials][update-cluster-new-service-principal-credentials]. This step is necessary to update the service principal on your AKS cluster.
58
-
59
-
>[!IMPORTANT]
60
-
>For large clusters, updating your AKS cluster with a new service principal may take a long time to complete. Consider reviewing and customizing the [node surge upgrade settings][node-surge-upgrade] to minimize disruption during the update. For small and midsize clusters, it takes a several minutes for the new credentials to update in the cluster.
57
+
Next, you [update AKS cluster with existing service principal credentials][update-cluster-new-service-principal-credentials]. This step is necessary to update the service principal on your AKS cluster.
61
58
62
59
### Create a new service principal
63
60
@@ -81,21 +78,21 @@ The output is similar to the following example output. Make a note of your own `
81
78
}
82
79
```
83
80
84
-
Define variables for the service principal ID and client secret using your output from running the [`az ad sp create-for-rbac`][az-ad-sp-create] command. The *SP_ID* is your*appId*, and the *SP_SECRET* is your *password*.
81
+
Define variables for the service principal ID and client secret using your output from running the [`az ad sp create-for-rbac`][az-ad-sp-create] command. The *SP_ID* is the*appId*, and the *SP_SECRET* is your *password*.
85
82
86
83
```console
87
84
SP_ID=7d837646-b1f3-443d-874c-fd83c7c739c5
88
85
SP_SECRET=a5ce83c9-9186-426d-9183-614597c7f2f7
89
86
```
90
87
91
-
Next, you can [update AKS cluster with new service principal credentials][update-cluster-new-service-principal-credentials]. This step is necessary for the Service Principal changes to reflect on the AKS cluster.
88
+
Next, you [update AKS cluster with new service principal credentials][update-cluster-new-service-principal-credentials]. This step is necessary for the Service Principal changes to reflect on the AKS cluster.
92
89
93
-
## Update AKS cluster with new service principal credentials
90
+
## Update AKS cluster with service principal credentials
94
91
95
-
>[!IMPORTANT]
96
-
>For large clusters, updating the AKS cluster with a new service principal may take a long time to complete. Consider reviewing and customizing the [node surge upgrade settings][node-surge-upgrade] to minimize disruption during cluster updates and upgrades. For small and midsize clusters, it takes a few moments for the new credentials to update in the cluster.
92
+
>[!IMPORTANT]
93
+
>For large clusters, updating your AKS cluster with a new service principal may take a long time to complete. Consider reviewing and customizing the [node surge upgrade settings][node-surge-upgrade] to minimize disruption during the update. For small and midsize clusters, it takes a several minutes for the new credentials to update in the cluster.
97
94
98
-
Update the AKS cluster with your new credentials using the [`az aks update-credentials`][az-aks-update-credentials] command.
95
+
Update the AKS cluster with your new or existing credentials by running the [`az aks update-credentials`][az-aks-update-credentials] command.
99
96
100
97
```azurecli-interactive
101
98
az aks update-credentials \
@@ -136,5 +133,5 @@ In this article, you learned how to update or rotate service principal and Azure
0 commit comments