Skip to content

Commit 7fd352a

Browse files
committed
updated optout hybrid
1 parent ed95e9b commit 7fd352a

File tree

1 file changed

+29
-2
lines changed

1 file changed

+29
-2
lines changed

articles/azure-monitor/insights/container-insights-optout-hybrid.md

Lines changed: 29 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,9 +12,36 @@ After you enable monitoring of your Kubernetes cluster running on Azure Stack or
1212

1313
## How to stop monitoring using Helm
1414

15-
To stop monitoring your hybrid Kubernetes cluster, you use the `Helm delete` command.
15+
To stop monitoring your hybrid Kubernetes cluster, run the following commands:
1616

17-
`helm delete <release name of azure monitor for containers>`
17+
1. To first identify the Azure Monitor for containers helm chart release installed on your cluster, run the following helm command.
18+
19+
```
20+
helm list
21+
```
22+
23+
The output will resemble the following:
24+
25+
```
26+
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
27+
azmon-containers-release-1 default 3 2020-04-21 15:27:24.1201959 -0700 PDT deployed azuremonitor-containers-2.7.0 7.0.0-1
28+
```
29+
30+
*azmon-containers-release-1* represents the helm chart release for Azure Monitor for containers.
31+
32+
2. To delete the chart release, run the following helm command.
33+
34+
`helm delete <release name of azure monitor for containers>`
35+
36+
Example:
37+
38+
`helm delete azmon-containers-release-1`
39+
40+
This will remove the release from the cluster. You can verify by running the `helm list` command:
41+
42+
```
43+
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
44+
```
1845
1946
The configuration change can take a few minutes to complete. Because Helm tracks your releases even after you’ve deleted them, you can audit a cluster’s history, and even undelete a release with `helm rollback`.
2047

0 commit comments

Comments
 (0)