Updating tabs

docs/en/installation/other-installation-methods/air-gap/launch-kubernetes/launch-kubernetes.md

@@ -15,8 +15,8 @@ Rancher can be installed on any Kubernetes cluster, including hosted Kubernetes
 
 The steps to set up an air-gapped Kubernetes cluster on RKE, RKE2, or K3s are shown below.
 
-{{% tabs %}}
-{{% tab "K3s" %}}
+<Tabs>
+<TabItem label="K3s">
 
 In this guide, we are assuming you have created your nodes in your air gapped environment and have a secure Docker private registry on your bastion server.
 
@@ -143,8 +143,8 @@ Upgrading an air-gap environment can be accomplished in the following manner:
 1. Download the new air-gap images (tar file) from the [releases](https://github.com/k3s-io/k3s/releases) page for the version of K3s you will be upgrading to. Place the tar in the `/var/lib/rancher/k3s/agent/images/` directory on each node. Delete the old tar file.
 2. Copy and replace the old K3s binary in `/usr/local/bin` on each node. Copy over the install script at https://get.k3s.io (as it is possible it has changed since the last release). Run the script again just as you had done in the past with the same environment variables.
 3. Restart the K3s service (if not restarted automatically by installer).
-{{% /tab %}}
-{{% tab "RKE2" %}}
+</TabItem>
+<TabItem label="RKE2">
 
 In this guide, we are assuming you have created your nodes in your air-gapped environment and have a secure Docker private registry on your bastion server.
 
@@ -279,8 +279,8 @@ Upgrading an air-gap environment can be accomplished in the following manner:
 1. Download the new air-gap artifacts and install script from the [releases](https://github.com/rancher/rke2/releases) page for the version of RKE2 you will be upgrading to.
 2. Run the script again just as you had done in the past with the same environment variables.
 3. Restart the RKE2 service.
-{{% /tab %}}
-{{% tab "RKE" %}}
+</TabItem>
+<TabItem label="RKE">
 We will create a Kubernetes cluster using Rancher Kubernetes Engine (RKE). Before being able to start your Kubernetes cluster, you’ll need to install RKE and create a RKE config file.
 
 ### 1. Install RKE
@@ -359,8 +359,8 @@ Save a copy of the following files in a secure location:
 - `rancher-cluster.yml`: The RKE cluster configuration file.
 - `kube_config_cluster.yml`: The [Kubeconfig file]({{<baseurl>}}/rke/latest/en/kubeconfig/) for the cluster, this file contains credentials for full access to the cluster.
 - `rancher-cluster.rkestate`: The [Kubernetes Cluster State file]({{<baseurl>}}/rke/latest/en/installation/#kubernetes-cluster-state), this file contains the current state of the cluster including the RKE configuration and the certificates.<br/><br/>_The Kubernetes Cluster State file is only created when using RKE v0.2.0 or higher._
-{{% /tab %}}
-{{% /tabs %}}
+</TabItem>
+</Tabs>
 
 :::note
 

docs/en/installation/other-installation-methods/air-gap/populate-private-registry/populate-private-registry.md

@@ -19,8 +19,8 @@ If the registry has certs, follow [this K3s documentation](https://rancher.com/d
 
 :::
 
-{{% tabs %}}
-{{% tab "Linux Only Clusters" %}}
+<Tabs>
+<TabItem label="Linux Only Clusters">
 
 For Rancher servers that will only provision Linux clusters, these are the steps to populate your private registry.
 
@@ -119,8 +119,8 @@ The `rancher-images.txt` is expected to be on the workstation in the same direct
    ```plain
    ./rancher-load-images.sh --image-list ./rancher-images.txt --registry <REGISTRY.YOURDOMAIN.COM:PORT>
    ```
-{{% /tab %}}
-{{% tab "Linux and Windows Clusters" %}}
+</TabItem>
+<TabItem label="Linux and Windows Clusters">
 
 For Rancher servers that will provision Linux and Windows clusters, there are distinctive steps to populate your private registry for the Windows images and the Linux images. Since a Windows cluster is a mix of Linux and Windows nodes, the Linux images pushed into the private registry are manifests.
 
@@ -305,8 +305,8 @@ The image list, `rancher-images.txt` or `rancher-windows-images.txt`, is expecte
 ```
 
 
-{{% /tab %}}
-{{% /tabs %}}
+</TabItem>
+</Tabs>
 
 ### [Next step for Kubernetes Installs - Launch a Kubernetes Cluster]({{<baseurl>}}/rancher/v2.6/en/installation/other-installation-methods/air-gap/launch-kubernetes/)
 

docs/en/installation/other-installation-methods/air-gap/prepare-nodes/prepare-nodes.md

@@ -11,8 +11,8 @@ The infrastructure depends on whether you are installing Rancher on a K3s Kubern
 
 Rancher can be installed on any Kubernetes cluster. The RKE and K3s Kubernetes infrastructure tutorials below are still included for convenience.
 
-{{% tabs %}}
-{{% tab "K3s" %}}
+<Tabs>
+<TabItem label="K3s">
 We recommend setting up the following infrastructure for a high-availability installation:
 
 - **Two Linux nodes,** typically virtual machines, in the infrastructure provider of your choice.
@@ -85,8 +85,8 @@ Rancher supports air gap installs using a private registry. You must have your o
 In a later step, when you set up your K3s Kubernetes cluster, you will create a [private registries configuration file]({{<baseurl>}}/k3s/latest/en/installation/private-registry/) with details from this registry.
 
 If you need help with creating a private registry, please refer to the [official Docker documentation.](https://docs.docker.com/registry/deploying/#run-an-externally-accessible-registry)
-{{% /tab %}}
-{{% tab "RKE" %}}
+</TabItem>
+<TabItem label="RKE">
 
 To install the Rancher management server on a high-availability RKE cluster, we recommend setting up the following infrastructure:
 
@@ -152,8 +152,8 @@ In a later step, when you set up your RKE Kubernetes cluster, you will create a
 
 If you need help with creating a private registry, please refer to the [official Docker documentation.](https://docs.docker.com/registry/deploying/#run-an-externally-accessible-registry)
 
-{{% /tab %}}
-{{% tab "Docker" %}}
+</TabItem>
+<TabItem label="Docker">
 
 :::note Notes:
 
@@ -177,7 +177,7 @@ Rancher supports air gap installs using a Docker private registry on your bastio
 
 If you need help with creating a private registry, please refer to the [official Docker documentation.](https://docs.docker.com/registry/)
 
-{{% /tab %}}
-{{% /tabs %}}
+</TabItem>
+</Tabs>
 
 ### [Next: Collect and Publish Images to your Private Registry]({{<baseurl>}}/rancher/v2.6/en/installation/other-installation-methods/air-gap/populate-private-registry/)

docs/en/installation/other-installation-methods/single-node-docker/single-node-upgrades/single-node-upgrades.md

@@ -133,8 +133,8 @@ To see the command to use when starting the new Rancher server container, choose
 - Docker Upgrade
 - Docker Upgrade for Air Gap Installs
 
-{{% tabs %}}
-{{% tab "Docker Upgrade" %}}
+<Tabs>
+<TabItem label="Docker Upgrade">
 
 Select which option you had installed Rancher server
 
@@ -265,8 +265,8 @@ Privileged access is [required.]({{<baseurl>}}/rancher/v2.6/en/installation/othe
 
 {{% /accordion %}}
 
-{{% /tab %}}
-{{% tab "Docker Air Gap Upgrade" %}}
+</TabItem>
+<TabItem label="Docker Air Gap Upgrade">
 
 For security purposes, SSL (Secure Sockets Layer) is required when using Rancher. SSL secures all Rancher network communication, like when you login or interact with a cluster.
 
@@ -371,8 +371,8 @@ docker run -d --volumes-from rancher-data \
 ```
 privileged access is [required.]({{<baseurl>}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/#privileged-access-for-rancher)
 {{% /accordion %}}
-{{% /tab %}}
-{{% /tabs %}}
+</TabItem>
+</Tabs>
 
 **Result:** You have upgraded Rancher. Data from your upgraded server is now saved to the `rancher-data` container for use in future upgrades.