Updating tabs

docs/en/pipelines/pipelines.md

@@ -119,8 +119,8 @@ Before you can start configuring a pipeline for your repository, you must config
 
 Select your provider's tab below and follow the directions.
 
-{{% tabs %}}
-{{% tab "GitHub" %}}
+<Tabs>
+<TabItem label="GitHub">
 
 1. In the upper left corner, click **☰ > Cluster Management**.
 1. Go to the cluster where you want to configure pipelines and click **Explore**.
@@ -132,8 +132,8 @@ Select your provider's tab below and follow the directions.
 1. If you're using GitHub for enterprise, select **Use a private github enterprise installation**. Enter the host address of your GitHub installation.
 1. Click **Authenticate**.
 
-{{% /tab %}}
-{{% tab "GitLab" %}}
+</TabItem>
+<TabItem label="GitLab">
 
 1. In the upper left corner, click **☰ > Cluster Management**.
 1. Go to the cluster where you want to configure pipelines and click **Explore**.
@@ -153,8 +153,8 @@ Select your provider's tab below and follow the directions.
 
 :::
 
-{{% /tab %}}
-{{% tab "Bitbucket Cloud" %}}
+</TabItem>
+<TabItem label="Bitbucket Cloud">
 
 1. In the upper left corner, click **☰ > Cluster Management**.
 1. Go to the cluster where you want to configure pipelines and click **Explore**.
@@ -166,8 +166,8 @@ Select your provider's tab below and follow the directions.
 1. From Bitbucket, copy the consumer **Key** and **Secret**. Paste them into Rancher.
 1. Click **Authenticate**.
 
-{{% /tab %}}
-{{% tab "Bitbucket Server" %}}
+</TabItem>
+<TabItem label="Bitbucket Server">
 
 1. In the upper left corner, click **☰ > Cluster Management**.
 1. Go to the cluster where you want to configure pipelines and click **Explore**.
@@ -188,8 +188,8 @@ Bitbucket server needs to do SSL verification when sending webhooks to Rancher.
 
 :::
 
-{{% /tab %}}
-{{% /tabs %}}
+</TabItem>
+</Tabs>
 
 **Result:** After the version control provider is authenticated, you will be automatically re-directed to start configuring which repositories you want start using with a pipeline.
 

docs/en/pipelines/storage/storage.md

@@ -27,8 +27,8 @@ This section assumes that you understand how persistent storage works in Kuberne
     - **Add Volume > Use an existing persistent volume (claim)**
 
 1.  Complete the form that displays to choose a persistent volume for the internal Docker registry.
-{{% tabs %}}
-{{% tab "Add a new persistent volume" %}}
+<Tabs>
+<TabItem label="Add a new persistent volume">
 <br/>
 1. Enter a **Name** for the volume claim.
 
@@ -41,9 +41,9 @@ This section assumes that you understand how persistent storage works in Kuberne
 
 1. Click **Define**.
 
-{{% /tab %}}
+</TabItem>
 
-{{% tab "Use an existing persistent volume" %}}
+<TabItem label="Use an existing persistent volume">
 <br/>
 1. Enter a **Name** for the volume claim.
 
@@ -53,9 +53,9 @@ This section assumes that you understand how persistent storage works in Kuberne
 
 1. Click **Define**.
 
-{{% /tab %}}
+</TabItem>
 
-{{% /tabs %}}
+</Tabs>
 
 1. From the **Mount Point** field, enter `/var/lib/registry`, which is the data storage path inside the Docker registry container.
 
@@ -74,9 +74,9 @@ This section assumes that you understand how persistent storage works in Kuberne
     - **Add Volume > Use an existing persistent volume (claim)**
 
 1.  Complete the form that displays to choose a persistent volume for the internal Docker registry.
-{{% tabs %}}
+<Tabs>
 
-{{% tab "Add a new persistent volume" %}}
+<TabItem label="Add a new persistent volume">
 <br/>
 1. Enter a **Name** for the volume claim.
 
@@ -89,8 +89,8 @@ This section assumes that you understand how persistent storage works in Kuberne
 
 1. Click **Define**.
 
-{{% /tab %}}
-{{% tab "Use an existing persistent volume" %}}
+</TabItem>
+<TabItem label="Use an existing persistent volume">
 <br/>
 1. Enter a **Name** for the volume claim.
 
@@ -100,8 +100,8 @@ This section assumes that you understand how persistent storage works in Kuberne
 
 1. Click **Define**.
 
-{{% /tab %}}
-{{% /tabs %}}
+</TabItem>
+</Tabs>
 
 1. From the **Mount Point** field, enter `/data`, which is the data storage path inside the Minio container.