From 14f35ed0b56e2252a17015cc89a2115273371180 Mon Sep 17 00:00:00 2001 From: Pavan Gudiwada Date: Mon, 2 Jun 2025 13:08:15 +0530 Subject: [PATCH] Updated disabling instructions --- docs/setup-robusta/alertsui.rst | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/docs/setup-robusta/alertsui.rst b/docs/setup-robusta/alertsui.rst index d8a87147e..cfc9c6b20 100644 --- a/docs/setup-robusta/alertsui.rst +++ b/docs/setup-robusta/alertsui.rst @@ -70,10 +70,17 @@ Choose the appropriate instructions below, based on whether you use the Promethe Disabling the Feature --------------------------------- -If you choose to stop using the Robusta Alerts UI, set ``enabledManagedConfiguration: false`` in ``generated_values.yaml`` and do a :ref:`Helm Upgrade `. +If you choose to stop using the Robusta Alerts UI -Modify and run the following command for all the Robusta rule custom resources present in your cluster. +1. Set ``enabledManagedConfiguration: false`` in ``generated_values.yaml`` and do a :ref:`Helm Upgrade `. +2. Identify the PrometheusRule custom resources added by Robusta .. code-block:: bash - kubectl delete prometheusrules.monitoring.coreos.com robusta-prometheus.rules--Value -n NameSpace + kubectl get prometheusrules -A | grep robusta-prometheus + +3. Modify and run the following command for all the Robusta rule custom resources present in your cluster. + +.. code-block:: bash + + kubectl delete prometheusrules.monitoring.coreos.com robusta-prometheus.rules -n