Skip to content

Commit 8a63a94

Browse files
Merge pull request #268701 from bwren/ci-arc
Update to Container insights Arc onboarding
2 parents b0caf73 + ed88f62 commit 8a63a94

File tree

1 file changed

+14
-5
lines changed

1 file changed

+14
-5
lines changed

articles/azure-monitor/containers/kubernetes-monitoring-enable.md

Lines changed: 14 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Enable monitoring for Azure Kubernetes Service (AKS) cluster
33
description: Learn how to enable Container insights and Managed Prometheus on an Azure Kubernetes Service (AKS) cluster.
44
ms.topic: conceptual
5-
ms.date: 11/14/2023
5+
ms.date: 03/11/2024
66
ms.custom: devx-track-azurecli
77
ms.reviewer: aul
88
---
@@ -351,7 +351,7 @@ az aks enable-addons -a monitoring -n <cluster-name> -g <cluster-resource-group-
351351
**Example**
352352

353353
```azurecli
354-
az aks enable-addons -a monitoring -n <cluster-name> -g <cluster-resource-group-name> --workspace-resource-id "/subscriptions/my-subscription/resourceGroups/my-resource-group/providers/Microsoft.OperationalInsights/workspaces/my-workspace"
354+
az aks enable-addons -a monitoring -n "my-cluster" -g "my-resource-group" --workspace-resource-id "/subscriptions/my-subscription/resourceGroups/my-resource-group/providers/Microsoft.OperationalInsights/workspaces/my-workspace"
355355
```
356356

357357

@@ -376,22 +376,31 @@ az k8s-extension create --name azuremonitor-containers --cluster-name <cluster-n
376376
377377
```
378378

379+
See the [resource requests and limits section of Helm chart](https://github.com/microsoft/Docker-Provider/blob/ci_prod/charts/azuremonitor-containers/values.yaml) for the available configuration settings.
380+
379381

380382
**Example**
381383

382384
```azurecli
383-
az aks enable-addons -a monitoring -n my-cluster -g my-resource-group --workspace-resource-id "/subscriptions/my-subscription/resourceGroups/my-resource-group/providers/Microsoft.OperationalInsights/workspaces/my-workspace"
385+
az k8s-extension create --name azuremonitor-containers --cluster-name "my-cluster" --resource-group "my-resource-group" --cluster-type connectedClusters --extension-type Microsoft.AzureMonitor.Containers --configuration-settings logAnalyticsWorkspaceResourceID="/subscriptions/my-subscription/resourceGroups/my-resource-group/providers/Microsoft.OperationalInsights/workspaces/my-workspace"
384386
```
385387

386-
387-
See the [resource requests and limits section of Helm chart](https://github.com/microsoft/Docker-Provider/blob/ci_prod/charts/azuremonitor-containers/values.yaml) for the available configuration settings.
388+
**Arc-enabled cluster with forward proxy**
388389

389390
If the cluster is configured with a forward proxy, then proxy settings are automatically applied to the extension. In the case of a cluster with AMPLS + proxy, proxy config should be ignored. Onboard the extension with the configuration setting `amalogs.ignoreExtensionProxySettings=true`.
390391

391392
```azurecli
392393
az k8s-extension create --name azuremonitor-containers --cluster-name <cluster-name> --resource-group <resource-group> --cluster-type connectedClusters --extension-type Microsoft.AzureMonitor.Containers --configuration-settings amalogs.ignoreExtensionProxySettings=true
393394
```
394395

396+
**Arc-enabled cluster with ARO or OpenShift or Windows nodes**
397+
398+
Managed identity authentication is not supported for Arc-enabled Kubernetes clusters with ARO (Azure Red Hat OpenShift) or OpenShift or Windows nodes. Use legacy authentication by specifying `amalogs.useAADAuth=false` as in the following example.
399+
400+
```azurecli
401+
az k8s-extension create --name azuremonitor-containers --cluster-name <cluster-name> --resource-group <resource-group> --cluster-type connectedClusters --extension-type Microsoft.AzureMonitor.Containers --configuration-settings amalogs.useAADAuth=false
402+
```
403+
395404
**Delete extension instance**
396405

397406
The following command only deletes the extension instance, but doesn't delete the Log Analytics workspace. The data in the Log Analytics resource is left intact.

0 commit comments

Comments
 (0)