Updating tabs

versioned_docs/version-2.6/v2.6/en/monitoring-alerting/configuration/receiver/receiver.md

@@ -32,8 +32,8 @@ The [Alertmanager Config](https://prometheus.io/docs/alerting/latest/configurati
 
 To create notification receivers in the Rancher UI,
 
-{{% tabs %}}
-{{% tab "Rancher v2.6.5+" %}}
+<Tabs>
+<TabItem label="Rancher v2.6.5+">
 
 1. Go to the cluster where you want to create receivers. Click **Monitoring -> Alerting -> AlertManagerConfigs**.
 1. Ciick **Create**.
@@ -42,16 +42,16 @@ To create notification receivers in the Rancher UI,
 1. Configure one or more providers for the receiver. For help filling out the forms, refer to the configuration options below.
 1. Click **Create**.
 
-{{% /tab %}}
-{{% tab "Rancher before v2.6.5" %}}
+</TabItem>
+<TabItem label="Rancher before v2.6.5">
 
 1. Go to the cluster where you want to create receivers. Click **Monitoring** and click **Receiver**.
 2. Enter a name for the receiver.
 3. Configure one or more providers for the receiver. For help filling out the forms, refer to the configuration options below.
 4. Click **Create**.
 
-{{% /tab %}}
-{{% /tabs %}}
+</TabItem>
+</Tabs>
 
 **Result:** Alerts can be configured to send notifications to the receiver(s).
 

versioned_docs/version-2.6/v2.6/en/monitoring-alerting/configuration/route/route.md

@@ -42,8 +42,8 @@ The route needs to refer to a [receiver](#receiver-configuration) that has alrea
 
 ### Grouping
 
-{{% tabs %}}
-{{% tab "Rancher v2.6.5+" %}}
+<Tabs>
+<TabItem label="Rancher v2.6.5+">
 
 > **Note** As of Rancher v2.6.5 `Group By` now accepts a list of strings instead of key-value pairs. See the [upstream documentation](https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/api.md#route) for details.
 
@@ -54,8 +54,8 @@ The route needs to refer to a [receiver](#receiver-configuration) that has alrea
 | Group Interval | 5m | How long to wait before sending an alert that has been added to a group of alerts for which an initial notification has already been sent. |
 | Repeat Interval |  4h | How long to wait before re-sending a given alert that has already been sent. |
 
-{{% /tab %}}
-{{% tab "Rancher before v2.6.5" %}}
+</TabItem>
+<TabItem label="Rancher before v2.6.5">
 
 | Field |    Default | Description |
 |-------|--------------|---------|
@@ -64,8 +64,8 @@ The route needs to refer to a [receiver](#receiver-configuration) that has alrea
 | Group Interval | 5m | How long to wait before sending an alert that has been added to a group of alerts for which an initial notification has already been sent. |
 | Repeat Interval |  4h | How long to wait before re-sending a given alert that has already been sent. |
 
-{{% /tab %}}
-{{% /tabs %}}
+</TabItem>
+</Tabs>
 
 
 

versioned_docs/version-2.6/v2.6/en/monitoring-alerting/guides/persist-grafana/persist-grafana.md

@@ -10,8 +10,8 @@ To allow the Grafana dashboard to persist after the Grafana instance restarts, a
 
 # Creating a Persistent Grafana Dashboard
 
-{{% tabs %}}
-{{% tab "Rancher v2.5.8+" %}}
+<Tabs>
+<TabItem label="Rancher v2.5.8+">
 
 > **Prerequisites:**
 > 
@@ -82,8 +82,8 @@ grafana.sidecar.dashboards.searchNamespace=ALL
 
 Note that the RBAC roles exposed by the Monitoring chart to add Grafana Dashboards are still restricted to giving permissions for users to add dashboards in the namespace defined in `grafana.dashboards.namespace`, which defaults to `cattle-dashboards`.
 
-{{% /tab %}}
-{{% tab "Rancher before v2.5.8" %}}
+</TabItem>
+<TabItem label="Rancher before v2.5.8">
 > **Prerequisites:**
 > 
 > - The monitoring application needs to be installed.
@@ -124,8 +124,8 @@ To prevent the persistent dashboard from being deleted when Monitoring v2 is uni
 helm.sh/resource-policy: "keep"
 ```
 
-{{% /tab %}}
-{{% /tabs %}}
+</TabItem>
+</Tabs>
 
 # Known Issues