Updating tabs

docs/en/cluster-admin/certificate-rotation/certificate-rotation.md

@@ -13,8 +13,8 @@ By default, Kubernetes clusters require certificates and Rancher launched Kubern
 
 Certificates can be rotated for the following services:
 
-{{% tabs %}}
-{{% tab "RKE" %}}
+<Tabs>
+<TabItem label="RKE">
 
 - etcd
 - kubelet (node certificate)
@@ -24,8 +24,8 @@ Certificates can be rotated for the following services:
 - kube-scheduler
 - kube-controller-manager
 
-{{% /tab %}}
-{{% tab "RKE2" %}}
+</TabItem>
+<TabItem label="RKE2">
 
 - admin
 - api-server
@@ -39,8 +39,8 @@ Certificates can be rotated for the following services:
 - kubelet
 - kube-proxy
 
-{{% /tab %}}
-{{% /tabs %}}
+</TabItem>
+</Tabs>
 
 :::note
 
@@ -65,15 +65,15 @@ Rancher launched Kubernetes clusters have the ability to rotate the auto-generat
 
 ### Additional Notes
 
-{{% tabs %}}
-{{% tab "RKE" %}}
+<Tabs>
+<TabItem label="RKE">
 
 Even though the RKE CLI can use custom certificates for the Kubernetes cluster components, Rancher currently doesn't allow the ability to upload these in Rancher launched Kubernetes clusters.
 
-{{% /tab %}}
-{{% tab "RKE2" %}}
+</TabItem>
+<TabItem label="RKE2">
 
 In RKE2, both etcd and control plane nodes are treated as the same `server` concept. As such, when rotating certificates of services specific to either of these components will result in certificates being rotated on both. The certificates will only change for the specified service, but you will see nodes for both components go into an updating state. You may also see worker only nodes go into an updating state. This is to restart the workers after a certificate change to ensure they get the latest client certs.
 
-{{% /tab %}}
-{{% /tabs %}}
+</TabItem>
+</Tabs>