Updating tabs

versioned_docs/version-2.5/v2.5/en/logging/custom-resource-config/flows/flows.md

@@ -10,8 +10,8 @@ For the full details on configuring `Flows` and `ClusterFlows`, see the [Banzai
 
 # Configuration
 
-{{% tabs %}}
-{{% tab "Rancher v2.5.8+" %}}
+<Tabs>
+<TabItem label="Rancher v2.5.8+">
 
 - [Flows](#flows-2-5-8)
   - [Matches](#matches-2-5-8)
@@ -73,8 +73,8 @@ Matches, filters and `Outputs` are configured for `ClusterFlows` in the same way
 
 After `ClusterFlow` selects logs from all namespaces in the cluster, logs from the cluster will be collected and logged to the selected `ClusterOutput`.
 
-{{% /tab %}}
-{{% tab "Rancher before v2.5.8" %}}
+</TabItem>
+<TabItem label="Rancher before v2.5.8">
 
 - [Flows](#flows-2-5-0)
   - [Matches](#matches-2-5-0)
@@ -130,8 +130,8 @@ Matches, filters and `Outputs` are also configured for `ClusterFlows`. The only
 
 `ClusterFlows` need to be defined in YAML.
 
-{{% /tab %}}
-{{% /tabs %}}
+</TabItem>
+</Tabs>
 
 
 # YAML Example

versioned_docs/version-2.5/v2.5/en/logging/custom-resource-config/outputs/outputs.md

@@ -14,8 +14,8 @@ For the full details on configuring `Outputs` and `ClusterOutputs`, see the [Ban
 
 # Configuration
 
-{{% tabs %}}
-{{% tab "v2.5.8+" %}}
+<Tabs>
+<TabItem label="v2.5.8+">
 
 - [Outputs](#outputs-2-5-8)
 - [ClusterOutputs](#clusteroutputs-2-5-8)
@@ -68,8 +68,8 @@ For example configuration for each logging plugin supported by the logging opera
 
 For the details of the `ClusterOutput` custom resource, see [ClusterOutput.](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/crds/v1beta1/clusteroutput_types/)
 
-{{% /tab %}}
-{{% tab "Rancher before v2.5.8" %}}
+</TabItem>
+<TabItem label="Rancher before v2.5.8">
 
 
 - [Outputs](#outputs-2-5-0)
@@ -101,8 +101,8 @@ The Rancher UI provides forms for configuring the `ClusterOutput` type, target,
 
 For example configuration for each logging plugin supported by the logging operator, see the [logging operator documentation.](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/plugins/outputs/)
 
-{{% /tab %}}
-{{% /tabs %}}
+</TabItem>
+</Tabs>
 
 
 # YAML Examples

versioned_docs/version-2.5/v2.5/en/logging/logging.md

@@ -80,20 +80,20 @@ For a list of options that can be configured when the logging application is ins
 
 ### Windows Support
 
-{{% tabs %}}
-{{% tab "Rancher v2.5.8+" %}}
+<Tabs>
+<TabItem label="Rancher v2.5.8+">
 As of Rancher v2.5.8, logging support for Windows clusters has been added and logs can be collected from Windows nodes.
 
 For details on how to enable or disable Windows node logging, see [this section.](./helm-chart-options/#enable-disable-windows-node-logging)
 
-{{% /tab %}}
-{{% tab "Rancher before v2.5.8" %}}
+</TabItem>
+<TabItem label="Rancher before v2.5.8">
 Clusters with Windows workers support exporting logs from Linux nodes, but Windows node logs are currently unable to be exported.
 Only Linux node logs are able to be exported.
 
 To allow the logging pods to be scheduled on Linux nodes, tolerations must be added to the pods. Refer to the [Working with Taints and Tolerations]({{<baseurl>}}/rancher/v2.5/en/logging/taints-tolerations/) section for details and an example.
-{{% /tab %}}
-{{% /tabs %}}
+</TabItem>
+</Tabs>
 
 
 ### Working with a Custom Docker Root Directory

versioned_docs/version-2.5/v2.5/en/logging/taints-tolerations/taints-tolerations.md

@@ -19,20 +19,20 @@ Both provide choice for the what node(s) the pod will run on.
 
 ### Default Implementation in Rancher's Logging Stack
 
-{{% tabs %}}
-{{% tab "Rancher v2.5.8+" %}}
+<Tabs>
+<TabItem label="Rancher v2.5.8+">
 By default, Rancher taints all Linux nodes with `cattle.io/os=linux`, and does not taint Windows nodes.
 The logging stack pods have `tolerations` for this taint, which enables them to run on Linux nodes.
 Moreover, most logging stack pods run on Linux only and have a `nodeSelector` added to ensure they run on Linux nodes.
 
-{{% /tab %}}
-{{% tab "Rancher before v2.5.8" %}}
+</TabItem>
+<TabItem label="Rancher before v2.5.8">
 By default, Rancher taints all Linux nodes with `cattle.io/os=linux`, and does not taint Windows nodes.
 The logging stack pods have `tolerations` for this taint, which enables them to run on Linux nodes.
 Moreover, we can populate the `nodeSelector` to ensure that our pods *only* run on Linux nodes.
 
-{{% /tab %}}
-{{% /tabs %}}
+</TabItem>
+</Tabs>
 
 This example Pod YAML file shows a nodeSelector being used with a toleration: