How to uninstall the Site24x7 Kubernetes monitoring agent

How to uninstall the Site24x7 Kubernetes monitoring agent

Execute the below commands to uninstall the Site24x7 Kubernetes monitoring agent from your cluster:

  • Deletion command for the DaemonSet agent deployed using a YAML file:

            kubectl delete -f site24x7-agent.yaml


or

            kubectl delete ds,sa site24x7-agent -n <namespace>; \

            kubectl delete clusterrole,clusterrolebinding site24x7; 

or

            kubectl delete ds,sa,clusterrole,clusterrolebinding -A -l app.kubernetes.io/owner=site24x7

Input your namespace instead of <namespace>.

  • Deletion command for kube-state-metrics deployed using a YAML file:

            kubectl delete -f site24x7-kube-state-metrics.yaml

or 

            kubectl delete deploy,sa kube-state-metrics -n kube-system; \

            kubectl delete clusterrole,clusterrolebinding kube-state-metrics;

or 

            kubectl delete deploy,sa,clusterrole,clusterrolebinding -A -l app.kubernetes.io/name=site24x7-kube-state-metrics

 

  • Deletion command for a DaemonSet agent deployed using Helm:


           helm uninstall <release_name>\

           helm repo remove site24x7

Input your release name instead of <release_name>.

 


    • Related Articles

    • How to uninstall the Site24x7 Windows Server Monitoring Agent

      Method 1: To uninstall the Site24x7 Windows Server Monitoring Agent, click the link below: https://staticdownloads.site24x7.com/server/Site24x7WindowsAgentUninstall.zip Unzip and execute the Uninstall.bat file in the Command Prompt as an ...

    • Bundled .NET and .NET Core agents in a single MSI

      In APM Insight .NET agent version 6.8.0, the .NET and .NET Core agents have been bundled into a single MSI, enabling unified monitoring of both application types. Upgrade requirements for .NET Core agent 6.7 and below If you're using .NET Core agent ...

    • Troubleshooting false positive alerts in monitoring

      Problem False positive alerts are being generated. Possible cause The monitoring system is down in some locations. The Website monitor might be configured for one location, such as Seattle, but may appear down when accessed from another location, ...

    • Unable to add SQL insight monitor

      If the SQL Insight monitor is not getting added even after entering your credentials, try these troubleshooting steps: Ensure that the Auto-discover applications feature is enabled. If not, you will need to trigger discovery using the Discover ...

    • How does Site24x7 always ensure the availability of its location agents during monitoring?

      Site24x7 uses a preferred location recheck logic in the back-end to ensure the availability of all monitoring locations. This logic is only applied when you've disabled the option "Restrict monitoring within selected locations" in the Add or Edit ...