Skip to content

Commit f024afc

Browse files
authored
Update container-insights-troubleshoot.md
1 parent 7f2cfa7 commit f024afc

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/azure-monitor/containers/container-insights-troubleshoot.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -157,14 +157,14 @@ To view the non-Azure Kubernetes cluster in Container insights, Read access is r
157157
```
158158
159159
## Installation of Azure Monitor Containers Extension fail with an error containing “manifests contain a resource that already exists” on Azure Arc Enabled Kubernetes cluster
160-
The error _manifests contain a resource that already exists_ indicates that resources of the Container Insights agent already exist on the Azure Arc Enabled Kubernetes cluster. This indicates that the container insights agent is already installed either through azuremonitor-containers HELM chart or Monitoring Addon if it is AKS Cluster which is connected Azure Arc. The solution to this issue, is to clean up the existing resources of container insights agent if its exists and then enable Azure Monitor Containers Extension.
160+
The error _manifests contain a resource that already exists_ indicates that resources of the Container Insights agent already exist on the Azure Arc Enabled Kubernetes cluster. This indicates that the container insights agent is already installed either through azuremonitor-containers HELM chart or Monitoring Addon if it is AKS Cluster which is connected Azure Arc. The solution to this issue, is to clean up the existing resources of container insights agent if it exists and then enable Azure Monitor Containers Extension.
161161
162162
### For non-AKS clusters
163163
1. Against the K8s cluster which is connected to Azure Arc, run below command to verify whether the azmon-containers-release-1 helm chart release exists or not:
164164
165165
`helm list -A`
166166
167-
2. If the output of the above command indicates that azmon-containers-release-1 exists and then delete the helm chart release:
167+
2. If the output of the above command indicates that azmon-containers-release-1 exists, delete the helm chart release:
168168
169169
`helm del azmon-containers-release-1`
170170

0 commit comments

Comments
 (0)