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/learn/quick-kubernetes-deploy-cli.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -75,10 +75,10 @@ The following example creates a resource group named *myResourceGroup* in the *e
75
75
76
76
The following example creates a cluster named *myAKSCluster* with one node and enables a system-assigned managed identity.
77
77
78
-
* Create an AKS cluster using the [`az aks create`][az-aks-create] command with the `--enable-addons monitoring` and `--enable-msi-auth-for-monitoring` parameters to enable [Azure Monitor Container insights][azure-monitor-containers] with managed identity authentication (preview).
78
+
* Create an AKS cluster using the [`az aks create`][az-aks-create] command with the `--enable-addons monitoring` parameter to enable [Azure Monitor Container insights][azure-monitor-containers] with managed identity authentication (Minimum Azure CLI version 2.49.0 or higher).
79
79
80
80
```azurecli-interactive
81
-
az aks create -g myResourceGroup -n myAKSCluster --enable-managed-identity --node-count 1 --enable-addons monitoring --enable-msi-auth-for-monitoring --generate-ssh-keys
81
+
az aks create -g myResourceGroup -n myAKSCluster --enable-managed-identity --node-count 1 --enable-addons monitoring --generate-ssh-keys
82
82
```
83
83
84
84
After a few minutes, the command completes and returns JSON-formatted information about the cluster.
Copy file name to clipboardExpand all lines: articles/azure-monitor/containers/container-insights-cost-config.md
+9-3Lines changed: 9 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -125,20 +125,26 @@ Create a file and provide values for _interval_, _namespaceFilteringMode_, and _
125
125
126
126
## Onboarding to a new AKS cluster
127
127
128
+
> [!NOTE]
129
+
> Minimum Azure CLI version 2.49.0 or higher.
130
+
128
131
Use the following command to enable monitoring of your AKS cluster
129
132
130
133
```azcli
131
-
az aks create -g myResourceGroup -n myAKSCluster --enable-managed-identity --node-count 1 --enable-addons monitoring --enable-msi-auth-for-monitoring --data-collection-settings dataCollectionSettings.json --generate-ssh-keys
134
+
az aks create -g myResourceGroup -n myAKSCluster --enable-managed-identity --node-count 1 --enable-addons monitoring --data-collection-settings dataCollectionSettings.json --generate-ssh-keys
132
135
```
133
136
134
137
## Onboarding to an existing AKS Cluster
135
138
136
139
## [Azure CLI](#tab/create-CLI)
137
140
141
+
> [!NOTE]
142
+
> Minimum Azure CLI version 2.49.0 or higher.
143
+
138
144
### Onboard to a cluster without the monitoring addon
139
145
140
146
```azcli
141
-
az aks enable-addons -a monitoring --enable-msi-auth-for-monitoring -g <clusterResourceGroup> -n <clusterName> --data-collection-settings dataCollectionSettings.json
147
+
az aks enable-addons -a monitoring -g <clusterResourceGroup> -n <clusterName> --data-collection-settings dataCollectionSettings.json
142
148
```
143
149
144
150
### Onboard to a cluster with an existing monitoring addon
@@ -151,7 +157,7 @@ az aks show -g <clusterResourceGroup> -n <clusterName> | grep -i "logAnalyticsWo
151
157
az aks disable-addons -a monitoring -g <clusterResourceGroup> -n <clusterName>
152
158
153
159
# enable monitoring with data collection settings
154
-
az aks enable-addons -a monitoring --enable-msi-auth-for-monitoring -g <clusterResourceGroup> -n <clusterName> --workspace-resource-id <logAnalyticsWorkspaceResourceId> --data-collection-settings dataCollectionSettings.json
160
+
az aks enable-addons -a monitoring -g <clusterResourceGroup> -n <clusterName> --workspace-resource-id <logAnalyticsWorkspaceResourceId> --data-collection-settings dataCollectionSettings.json
Copy file name to clipboardExpand all lines: articles/azure-monitor/containers/container-insights-enable-aks.md
+9-3Lines changed: 9 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@ Use any of the following methods to enable monitoring for an existing AKS cluste
30
30
## [CLI](#tab/azure-cli)
31
31
32
32
> [!NOTE]
33
-
> Azure CLI version 2.39.0 or higher is required for managed identity authentication.
33
+
> Managed identity authentication will be default in CLI version 2.49.0 or higher. If you need to use legacy/non-managed identity authentication, use CLI version < 2.49.0.
34
34
35
35
### Use a default Log Analytics workspace
36
36
@@ -338,6 +338,9 @@ This section explains two methods for migrating to managed identity authenticati
338
338
339
339
AKS clusters with a service principal must first disable monitoring and then upgrade to managed identity. Only Azure public cloud, Azure China cloud, and Azure Government cloud are currently supported for this migration.
340
340
341
+
> [!NOTE]
342
+
> Minimum Azure CLI version 2.49.0 or higher.
343
+
341
344
1. Get the configured Log Analytics workspace resource ID:
342
345
343
346
```cli
@@ -359,13 +362,16 @@ AKS clusters with a service principal must first disable monitoring and then upg
359
362
1. Enable the monitoring add-on with the managed identity authentication option by using the Log Analytics workspace resource ID obtained in step 1:
360
363
361
364
```cli
362
-
az aks enable-addons -a monitoring --enable-msi-auth-for-monitoring -g <resource-group-name> -n <cluster-name> --workspace-resource-id <workspace-resource-id>
365
+
az aks enable-addons -a monitoring -g <resource-group-name> -n <cluster-name> --workspace-resource-id <workspace-resource-id>
363
366
```
364
367
365
368
### Existing clusters with system or user-assigned identity
366
369
367
370
AKS clusters with system-assigned identity must first disable monitoring and then upgrade to managed identity. Only Azure public cloud, Azure China cloud, and Azure Government cloud are currently supported for clusters with system identity. For clusters with user-assigned identity, only Azure public cloud is supported.
368
371
372
+
> [!NOTE]
373
+
> Minimum Azure CLI version 2.49.0 or higher.
374
+
369
375
1. Get the configured Log Analytics workspace resource ID:
370
376
371
377
```cli
@@ -381,7 +387,7 @@ AKS clusters with system-assigned identity must first disable monitoring and the
381
387
1. Enable the monitoring add-on with the managed identity authentication option by using the Log Analytics workspace resource ID obtained in step 1:
382
388
383
389
```cli
384
-
az aks enable-addons -a monitoring --enable-msi-auth-for-monitoring -g <resource-group-name> -n <cluster-name> --workspace-resource-id <workspace-resource-id>
390
+
az aks enable-addons -a monitoring -g <resource-group-name> -n <cluster-name> --workspace-resource-id <workspace-resource-id>
0 commit comments