Globally import Tabs and TabItem

2026-09-26 13:08:11 +00:00 · 2022-12-07 14:39:54 -08:00
parent 3d15613ef2
commit baf8137c7f
257 changed files with 131 additions and 594 deletions
@@ -2,7 +2,6 @@
 title: Release Notes
 ---

-
 ## Istio 1.5.8

 ### Important note on 1.5.x versions
@@ -2,9 +2,6 @@
 title: 4. Install Rancher
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 This section is about how to deploy Rancher for your air gapped environment. An air gapped environment could be where Rancher server will be installed offline, behind a firewall, or behind a proxy. There are _tabs_ for either a high availability (recommended) or a Docker installation.

 <Tabs>
@@ -2,9 +2,6 @@
 title: '2. Collect and Publish Images to your Private Registry'
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 > **Prerequisites:** You must have a [private registry](https://docs.docker.com/registry/deploying/) available to use.
 >
 > **Note:** Populating the private registry with images is the same process for HA and Docker installations, the differences in this section is based on whether or not you are planning to provision a Windows cluster or not.
@@ -2,9 +2,6 @@
 title: '1. Prepare your Node(s)'
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 This section is about how to prepare your node(s) to install Rancher for your air gapped environment. An air gapped environment could be where Rancher server will be installed offline, behind a firewall, or behind a proxy. There are _tabs_ for either a high availability (recommended) or a Docker installation.

 ## Prerequisites
@@ -2,9 +2,6 @@
 title: Upgrading Rancher Installed on Kubernetes with Helm 2
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 > Helm 3 has been released.  If you are using Helm 2, we recommend [migrating to Helm 3](https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/) because it is simpler to use and more secure than Helm 2.
 >
 > The [current instructions for Upgrading Rancher Installed on Kubernetes](../../../../pages-for-subheaders/upgrades.md) use Helm 3.
@@ -2,9 +2,6 @@
 title: Upgrading to v2.0.7+ — Namespace Migration
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 >This section applies only to Rancher upgrades from v2.0.6 or earlier to v2.0.7 or later. Upgrades from v2.0.7 to later version are unaffected.

 In Rancher v2.0.6 and prior, system namespaces crucial for Rancher and Kubernetes operations were not assigned to any Rancher project by default. Instead, these namespaces existed independently from all Rancher projects, but you could move these namespaces into any project without affecting cluster operations.
@@ -2,9 +2,6 @@
 title: '1. Set up Infrastructure and Private Registry'
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 In this section, you will provision the underlying infrastructure for your Rancher management server in an air gapped environment. You will also set up the private Docker registry that must be available to your Rancher node(s).

 An air gapped environment is an environment where the Rancher server is installed offline or behind a firewall.
@@ -2,9 +2,6 @@
 title: '3. Install Kubernetes (Skip for Docker Installs)'
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 > Skip this section if you are installing Rancher on a single node with Docker.

 This section describes how to install a Kubernetes cluster according to our [best practices for the Rancher server environment.](../../../../reference-guides/rancher-manager-architecture/architecture-recommendations.md#environment-for-kubernetes-installations) This cluster should be dedicated to run only the Rancher server.
@@ -2,9 +2,6 @@
 title: 4. Install Rancher
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 This section is about how to deploy Rancher for your air gapped environment. An air gapped environment could be where Rancher server will be installed offline, behind a firewall, or behind a proxy. There are _tabs_ for either a high availability (recommended) or a Docker installation.

 <Tabs>
@@ -2,9 +2,6 @@
 title: '2. Collect and Publish Images to your Private Registry'
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 This section describes how to set up your private registry so that when you install Rancher, Rancher will pull all the required images from this registry.

 By default, all images used to [provision Kubernetes clusters](../../../../pages-for-subheaders/kubernetes-clusters-in-rancher-setup.md) or launch any [tools](../../../../reference-guides/rancher-cluster-tools.md) in Rancher, e.g. monitoring, pipelines, alerts, are pulled from Docker Hub. In an air gapped installation of Rancher, you will need a private registry that is located somewhere accessible by your Rancher server. Then, you will load the registry with all the images.
@@ -2,9 +2,6 @@
 title: Upgrading Rancher Installed with Docker
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 The following instructions will guide you through upgrading a Rancher server that was installed with Docker.

 ## Prerequisites
@@ -2,9 +2,6 @@
 title: Choosing a Rancher Version
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 This section describes how to choose a Rancher version.

 For a high-availability installation of Rancher, which is recommended for production, the Rancher server is installed using a **Helm chart** on a Kubernetes cluster. Refer to the [Helm version requirements](./helm-version-requirements.md) to choose a version of Helm to install Rancher.
@@ -2,9 +2,6 @@
 title: Setting up Local System Charts for Air Gapped Installations
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 The [System Charts](https://github.com/rancher/system-charts) repository contains all the catalog items required for features such as monitoring, logging, alerting and global DNS.

 In an air gapped installation of Rancher, you will need to configure Rancher to use a local copy of the system charts. This section describes how to use local system charts using a CLI flag in Rancher v2.3.0, and using a Git mirror for Rancher versions before v2.3.0.
@@ -2,9 +2,6 @@
 title: Upgrading and Rolling Back Kubernetes
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 Following an upgrade to the latest version of Rancher, downstream Kubernetes clusters can be upgraded to use the latest supported version of Kubernetes.

 Rancher calls RKE (Rancher Kubernetes Engine) as a library when provisioning and editing RKE clusters. For more information on configuring the upgrade strategy for RKE clusters, refer to the [RKE documentation](https://rancher.com/docs/rke/latest/en/).
@@ -2,9 +2,6 @@
 title: Upgrading Kubernetes without Upgrading Rancher
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 _Available as of v2.3.0_

 The RKE metadata feature allows you to provision clusters with new versions of Kubernetes as soon as they are released, without upgrading Rancher. This feature is useful for taking advantage of patch versions of Kubernetes, for example, if you want to upgrade to Kubernetes v1.14.7 when your Rancher server originally supported v1.14.6.
@@ -2,9 +2,6 @@
 title: Custom Roles
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 Within Rancher, _roles_ determine what actions a user can make within a cluster or project.

 Note that _roles_ are different from _permissions_, which determine what clusters and projects you can access.
@@ -2,7 +2,6 @@
 title: Skip Tests
 ---

-
 You can define a set of tests that will be skipped by the CIS scan when the next report is generated.

 These tests will be skipped for subsequent CIS scans, including both manually triggered and scheduled scans, and the tests will be skipped with any profile.
@@ -2,9 +2,6 @@
 title: Backing up a Cluster
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 _Available as of v2.2.0_

 In the Rancher UI, etcd backup and recovery for [Rancher launched Kubernetes clusters](../../../pages-for-subheaders/launch-kubernetes-with-rancher.md) can be easily performed.
@@ -3,9 +3,6 @@ title: Removing Kubernetes Components from Nodes
 description: Learn about cluster cleanup when removing nodes from your Rancher-launched Kubernetes cluster. What is removed, how to do it manually
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 This section describes how to disconnect a node from a Rancher-launched Kubernetes cluster and remove all of the Kubernetes components from the node. This process allows you to use the node for other purposes.

 When you use Rancher to install Kubernetes on new nodes in an infrastructure provider, resources (containers/virtual network interfaces) and configuration items (certificates/configuration files) are created.
@@ -2,9 +2,6 @@
 title: Nodes and Node Pools
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 After you launch a Kubernetes cluster in Rancher, you can manage individual nodes from the cluster's **Node** tab. Depending on the [option used](../../../pages-for-subheaders/kubernetes-clusters-in-rancher-setup.md) to provision the cluster, there are different node options available.

 > If you want to manage the _cluster_ and not individual nodes, see [Editing Clusters](../../../pages-for-subheaders/cluster-configuration.md#editing-clusters-with-yaml).
@@ -2,9 +2,6 @@
 title: Restoring a Cluster from Backup
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 _Available as of v2.2.0_

 etcd backup and recovery for [Rancher launched Kubernetes clusters](../../../pages-for-subheaders/launch-kubernetes-with-rancher.md) can be easily performed. Snapshots of the etcd database are taken and saved either locally onto the etcd nodes or to a S3 compatible target. The advantages of configuring S3 is that if all etcd nodes are lost, your snapshot is saved remotely and can be used to restore the cluster.
@@ -2,7 +2,6 @@
 title: Backing up Rancher Installed with Docker
 ---

-
 After completing your Docker installation of Rancher, we recommend creating backups of it on a regular basis. Having a recent backup will let you recover quickly from an unexpected disaster.

 ### How to Read Placeholders
@@ -2,9 +2,6 @@
 title: Backing up Rancher Installed on an RKE Kubernetes Cluster
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 This section describes how to create backups of your high-availability Rancher install.

 In an RKE installation, the cluster data is replicated on each of three etcd nodes in the cluster, providing redundancy and data duplication in case one of the nodes fails.
@@ -3,9 +3,6 @@ title: Launching Catalog Apps
 ---


-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 Within a project, when you want to deploy applications from catalogs, the applications available in your project will be based on the [scope of the catalogs](../../../pages-for-subheaders/helm-charts-in-rancher.md#catalog-scopes).

 If your application is using ingresses, you can program the ingress hostname to an external DNS by setting up a [Global DNS entry](globaldns.md).
@@ -2,7 +2,6 @@
 title: Setting up a High-availability RKE Kubernetes Cluster
 ---

-
 This section describes how to install a Kubernetes cluster. This cluster should be dedicated to run only the Rancher server.

 For Rancher before v2.4, Rancher should be installed on an RKE Kubernetes cluster. RKE is a CNCF-certified Kubernetes distribution that runs entirely within Docker containers.
@@ -2,9 +2,6 @@
 title: Creating a DigitalOcean Cluster
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 In this section, you'll learn how to use Rancher to install an [RKE](https://rancher.com/docs/rke/latest/en/) Kubernetes cluster in DigitalOcean.

 First, you will set up your DigitalOcean cloud credentials in Rancher. Then you will use your cloud credentials to create a node template, which Rancher will use to provision new nodes in DigitalOcean.
@@ -3,9 +3,6 @@ title: Creating an Amazon EC2 Cluster
 description: Learn the prerequisites and steps required in order for you to create an Amazon EC2 cluster using Rancher
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 In this section, you'll learn how to use Rancher to install an [RKE](https://rancher.com/docs/rke/latest/en/) Kubernetes cluster in Amazon EC2.

 First, you will set up your EC2 cloud credentials in Rancher. Then you will use your cloud credentials to create a node template, which Rancher will use to provision new nodes in EC2.
@@ -2,9 +2,6 @@
 title: Creating an Azure Cluster
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 In this section, you'll learn how to install an [RKE](https://rancher.com/docs/rke/latest/en/) Kubernetes cluster in Azure through Rancher.

 First, you will set up your Azure cloud credentials in Rancher. Then you will use your cloud credentials to create a node template, which Rancher will use to provision new nodes in Azure.
@@ -3,9 +3,6 @@ title: Provisioning Kubernetes Clusters in vSphere
 ---


-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 In this section, you'll learn how to use Rancher to install an [RKE](https://rancher.com/docs/rke/latest/en/)  Kubernetes cluster in vSphere.

 First, you will set up your vSphere cloud credentials in Rancher. Then you will use your cloud credentials to create a node template, which Rancher will use to provision nodes in vSphere.
@@ -2,9 +2,6 @@
 title: Node Requirements for Rancher Managed Clusters
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 This page describes the requirements for the Rancher managed Kubernetes clusters where your apps and services will be installed. These downstream clusters should be separate from the three-node cluster running Rancher.

 > If Rancher is installed on a high-availability Kubernetes cluster, the Rancher server three-node cluster and downstream clusters have different requirements. For Rancher installation requirements, refer to the node requirements in the [installation section.](../../../pages-for-subheaders/installation-requirements.md)
@@ -2,9 +2,6 @@
 title: 2. Migrate Your Services
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 Although your services from v1.6 won't work in Rancher v2.x by default, that doesn't mean you have to start again from square one, manually rebuilding your applications in v2.x. To help with migration from v1.6 to v2.x, Rancher has developed a migration tool. The migration-tools CLI is a utility that helps you recreate your applications in Rancher v2.x. This tool exports your Rancher v1.6 services as Compose files and converts them to a Kubernetes manifest that Rancher v2.x can consume.

 Additionally, for each Rancher v1.6-specific Compose directive that cannot be consumed by Kubernetes, migration-tools CLI provides instructions on how to manually recreate them in Rancher v2.x.
@@ -2,9 +2,6 @@
 title: "4. Configure Health Checks"
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 Rancher v1.6 provided TCP and HTTP health checks on your nodes and services using its own health check microservice. These health checks monitored your containers to confirm they're operating as intended. If a container failed a health check, Rancher would destroy the unhealthy container and then replicates a healthy one to replace it.

 For Rancher v2.x, we've replaced the health check microservice, leveraging instead Kubernetes' native health check support.
@@ -2,5 +2,4 @@
 title: Authentication Config
 ---

-
 In the following tutorials, you will learn how to [manage users and groups](../how-to-guides/advanced-user-guides/authentication-permissions-and-global-configuration/about-authentication/authentication-config/manage-users-and-groups.md), [create local users](../how-to-guides/advanced-user-guides/authentication-permissions-and-global-configuration/about-authentication/authentication-config/create-local-users.md), [configure Google OAuth](../how-to-guides/advanced-user-guides/authentication-permissions-and-global-configuration/about-authentication/authentication-config/configure-google-oauth.md), [configure Active Directory (AD)](../how-to-guides/advanced-user-guides/authentication-permissions-and-global-configuration/about-authentication/authentication-config/configure-active-directory.md), [configure OpenLDAP](../pages-for-subheaders/configure-openldap.md), [configure FreeIPA](../how-to-guides/advanced-user-guides/authentication-permissions-and-global-configuration/about-authentication/authentication-config/configure-freeipa.md), [configure Azure AD](../how-to-guides/advanced-user-guides/authentication-permissions-and-global-configuration/about-authentication/authentication-config/configure-azure-ad.md), [configure GitHub](../how-to-guides/advanced-user-guides/authentication-permissions-and-global-configuration/about-authentication/authentication-config/configure-github.md), [configure Keycloak](../how-to-guides/advanced-user-guides/authentication-permissions-and-global-configuration/about-authentication/authentication-config/configure-keycloak.md), [configure PingIdentity (SAML)](../how-to-guides/advanced-user-guides/authentication-permissions-and-global-configuration/about-authentication/authentication-config/configure-pingidentity.md), [configure Okta (SAML)](../how-to-guides/advanced-user-guides/authentication-permissions-and-global-configuration/about-authentication/authentication-config/configure-okta-saml.md), [configure Shibboleth (SAML)](../pages-for-subheaders/configure-shibboleth-saml.md), and how to [configure Microsoft AD Federation Service (SAML)](../pages-for-subheaders/configure-microsoft-ad-federation-service-saml.md).
@@ -2,9 +2,6 @@
 title: Enabling Experimental Features
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 Rancher includes some features that are experimental and disabled by default. You might want to enable these features, for example, if you decide that the benefits of using an [unsupported storage type](../getting-started/installation-and-upgrade/advanced-options/enable-experimental-features/unsupported-storage-drivers.md) outweighs the risk of using an untested feature. Feature flags were introduced to allow you to try these features that are not enabled by default.

 The features can be enabled in three ways:
@@ -3,9 +3,6 @@ title: Install Rancher on a Kubernetes Cluster
 description: Learn how to install Rancher in development and production environments. Read about single node and high availability installation
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 ## Prerequisite

 Set up the Rancher server's local Kubernetes cluster.
@@ -3,9 +3,6 @@ title: Installation Requirements
 description: Learn the node requirements for each node running Rancher server when you’re configuring  Rancher to run either in a Docker or Kubernetes setup
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 This page describes the software, hardware, and networking requirements for the nodes where the Rancher server will be installed. The Rancher server can be installed on a single node or a high-availability Kubernetes cluster.

 > It is important to note that if you install Rancher on a Kubernetes cluster, requirements are different from the [node requirements for downstream user clusters,](../how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/node-requirements-for-rancher-managed-clusters.md) which will run your apps and services.
@@ -2,9 +2,6 @@
 title: Pipelines
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 Rancher's pipeline provides a simple CI/CD experience. Use it to automatically checkout code, run builds or scripts, publish Docker images or catalog applications, and deploy the updated software to users.

 Setting up a pipeline can help developers deliver new software as quickly and efficiently as possible. Using Rancher, you can integrate with a GitHub repository to setup a continuous integration (CI) pipeline.
@@ -2,9 +2,6 @@
 title: Upgrades
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 The following instructions will guide you through upgrading a Rancher server that was installed on a Kubernetes cluster with Helm. These steps also apply to air gap installs with Helm.

 For the instructions to upgrade Rancher installed with Docker, refer to [this page.](../getting-started/installation-and-upgrade/other-installation-methods/rancher-on-a-single-node-with-docker/upgrade-docker-installed-rancher.md)
@@ -2,9 +2,6 @@
 title: EC2 Node Template Configuration
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 For more details about EC2, nodes, refer to the official documentation for the [EC2 Management Console](https://aws.amazon.com/ec2).

 <Tabs>
@@ -2,9 +2,6 @@
 title: Azure Node Template Configuration
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 For more information about Azure, refer to the official [Azure documentation.](https://docs.microsoft.com/en-us/azure/?product=featured)

 <Tabs>
@@ -2,9 +2,6 @@
 title: DigitalOcean Node Template Configuration
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 <Tabs>
 <TabItem value="Rancher v2.2.0+">

@@ -2,7 +2,6 @@
 title: vSphere Node Template Configuration in Rancher before v2.0.4
 ---

-
 ## Account Access
 In the **Account Access** section, enter the vCenter FQDN or IP address and the credentials for the vSphere user account.

@@ -2,7 +2,6 @@
 title: vSphere Node Template Configuration in Rancher v2.0.4
 ---

-
 ## Account Access
 In the **Account Access** section, enter the vCenter FQDN or IP address and the credentials for the vSphere user account.

@@ -2,7 +2,6 @@
 title: vSphere Node Template Configuration in Rancher v2.2.0
 ---

-
 ## Account Access

 | Parameter                | Required | Description |
@@ -2,7 +2,6 @@
 title: vSphere Node Template Configuration in Rancher v2.3.3
 ---

-
 ## Account Access

 | Parameter                | Required | Description |
@@ -2,9 +2,6 @@
 title: Configuring Persistent Data for Pipeline Components
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 The pipelines' internal Docker registry and the Minio workloads use ephemeral volumes by default. This default storage works out-of-the-box and makes testing easy, but you lose the build images and build logs if the node running the Docker Registry or Minio fails. In most cases this is fine. If you want build images and logs to survive node failures, you can configure the Docker Registry and Minio to use persistent volumes.

 This section assumes that you understand how persistent storage works in Kubernetes. For more information, refer to the section on [how storage works.](../../how-to-guides/advanced-user-guides/manage-clusters/create-kubernetes-persistent-storage/manage-persistent-storage/about-persistent-storage.md)
@@ -2,9 +2,6 @@
 title: RKE Cluster Configuration Reference
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 When Rancher installs Kubernetes, it uses [RKE](../../../pages-for-subheaders/launch-kubernetes-with-rancher.md) as the Kubernetes distribution.

 This section covers the configuration options that are available in Rancher for a new or existing RKE Kubernetes cluster.
@@ -2,7 +2,6 @@
 title: Windows Support
 ---

-
 Prior to Rancher v2.5.6, the `agent` did not have native Windows manifests on downstream clusters with Windows nodes. This would result in a failing `agent` pod for the cluster.

 If you are upgrading from an older version of Rancher to v2.5.6+, you can deploy a working `agent` with the following workflow *in the downstream cluster*:
@@ -2,9 +2,6 @@
 title: Enable Istio with Pod Security Policies
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 If you have restrictive Pod Security Policies enabled, then Istio may not be able to function correctly, because it needs certain permissions in order to install itself and manage pod infrastructure. In this section, we will configure a cluster with PSPs enabled for an Istio install, and also set up the Istio CNI plugin.

 The Istio CNI plugin removes the need for each application pod to have a privileged `NET_ADMIN` container. For further information, see the [Istio CNI Plugin docs](https://istio.io/docs/setup/additional-setup/cni). Please note that the [Istio CNI Plugin is in alpha](https://istio.io/about/feature-stages/).
@@ -2,9 +2,6 @@
 title: CPU and Memory Allocations
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 This section describes the minimum recommended computing resources for the Istio components in a cluster.

 The CPU and memory allocations for each component are [configurable.](#configuring-resource-allocations)
@@ -2,9 +2,6 @@
 title: Flows and ClusterFlows
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 For the full details on configuring `Flows` and `ClusterFlows`, see the [Banzai Cloud Logging operator documentation.](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/output/)

 - [Configuration](#configuration)
@@ -2,9 +2,6 @@
 title: Outputs and ClusterOutputs
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 For the full details on configuring `Outputs` and `ClusterOutputs`, see the [Banzai Cloud Logging operator documentation.](https://banzaicloud.com/docs/one-eye/logging-operator/configuration/output/)


@@ -2,7 +2,6 @@
 title: rancher-logging Helm Chart Options
 ---

-
 ### Enable/Disable Windows Node Logging

 _Available as of v2.5.8_
@@ -2,9 +2,6 @@
 title: Working with Taints and Tolerations
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 "Tainting" a Kubernetes node causes pods to repel running on that node.

 Unless the pods have a `toleration` for that node's taint, they will run on other nodes in the cluster.
@@ -2,7 +2,6 @@
 title: How Monitoring Works
 ---

-
 ## 1. Architecture Overview

 _**The following sections describe how data flows through the Monitoring V2 application:**_
@@ -2,9 +2,6 @@
 title: Rendering the Helm Template in an Air Gapped Environment
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 > These instructions assume you have already followed the instructions for a Kubernetes upgrade on [this page,](upgrades.md) including the prerequisites, up until step 3. Upgrade Rancher.

 ## Rancher Helm Template Options
@@ -2,9 +2,6 @@
 title: Installing Rancher on a Google Kubernetes Engine Cluster
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 In this section, you'll learn how to install Rancher using Google Kubernetes Engine.

 If you already have a GKE Kubernetes cluster, skip to the step about [installing an ingress.](#7-install-an-ingress) Then install the Rancher Helm chart following the instructions on [this page.](../../../pages-for-subheaders/install-upgrade-on-a-kubernetes-cluster.md#install-the-rancher-helm-chart)
@@ -3,8 +3,6 @@ title: Port Requirements
 description: Read about port requirements needed in order for Rancher to operate properly, both for Rancher nodes and downstream Kubernetes cluster nodes
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
 import PortsIaasNodes from '@site/src/components/PortsIaasNodes'
 import PortsCustomNodes from '@site/src/components/PortsCustomNodes'
 import PortsImportedHosted from '@site/src/components/PortsImportedHosted'
@@ -2,9 +2,6 @@
 title: '1. Set up Infrastructure and Private Registry'
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 In this section, you will provision the underlying infrastructure for your Rancher management server in an air gapped environment. You will also set up the private Docker registry that must be available to your Rancher node(s).

 An air gapped environment is an environment where the Rancher server is installed offline or behind a firewall.
@@ -2,9 +2,6 @@
 title: '3. Install Kubernetes (Skip for Docker Installs)'
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 > Skip this section if you are installing Rancher on a single node with Docker.

 This section describes how to install a Kubernetes cluster according to our [best practices for the Rancher server environment.](../../../../reference-guides/rancher-manager-architecture/architecture-recommendations.md#environment-for-kubernetes-installations) This cluster should be dedicated to run only the Rancher server.
@@ -2,9 +2,6 @@
 title: 4. Install Rancher
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 This section is about how to deploy Rancher for your air gapped environment in a high-availability Kubernetes installation. An air gapped environment could be where Rancher server will be installed offline, behind a firewall, or behind a proxy.

 ### Privileged Access for Rancher v2.5+
@@ -2,9 +2,6 @@
 title: '2. Collect and Publish Images to your Private Registry'
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 This section describes how to set up your private registry so that when you install Rancher, Rancher will pull all the required images from this registry.

 By default, all images used to [provision Kubernetes clusters](../../../../pages-for-subheaders/kubernetes-clusters-in-rancher-setup.md) or launch any tools in Rancher, e.g. monitoring and logging, are pulled from Docker Hub. In an air gapped installation of Rancher, you will need a private registry that is located somewhere accessible by your Rancher server. Then, you will load the registry with all the images.
@@ -2,9 +2,6 @@
 title: Upgrading Rancher Installed with Docker
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 The following instructions will guide you through upgrading a Rancher server that was installed with Docker.

 ## Prerequisites
@@ -2,9 +2,6 @@
 title: Choosing a Rancher Version
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 This section describes how to choose a Rancher version.

 For a high-availability installation of Rancher, which is recommended for production, the Rancher server is installed using a **Helm chart** on a Kubernetes cluster. Refer to the [Helm version requirements](./helm-version-requirements.md) to choose a version of Helm to install Rancher.
@@ -2,9 +2,6 @@
 title: Configuring Azure AD
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 <Tabs>
 <TabItem value="Rancher v2.5.16+">

@@ -3,9 +3,6 @@ title: Configuring Keycloak (SAML)
 description: Create a Keycloak SAML client and configure Rancher to work with Keycloak. By the end your users will be able to sign into Rancher using their Keycloak logins
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 If your organization uses Keycloak Identity Provider (IdP) for user authentication, you can configure Rancher to allow your users to log in using their IdP credentials.

 ## Prerequisites
@@ -2,9 +2,6 @@
 title: Global Permissions
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 _Permissions_ are individual access rights that you can assign when selecting a custom permission for a user.

 Global Permissions define user authorization outside the scope of any particular cluster. Out-of-the-box, there are three default global permissions: `Administrator`, `Standard User` and `User-base`.
@@ -3,9 +3,6 @@ title: Removing Kubernetes Components from Nodes
 description: Learn about cluster cleanup when removing nodes from your Rancher-launched Kubernetes cluster. What is removed, how to do it manually
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 This section describes how to disconnect a node from a Rancher-launched Kubernetes cluster and remove all of the Kubernetes components from the node. This process allows you to use the node for other purposes.

 When you use Rancher to install Kubernetes on new nodes in an infrastructure provider, resources (containers/virtual network interfaces) and configuration items (certificates/configuration files) are created.
@@ -2,9 +2,6 @@
 title: Persistent Grafana Dashboards
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 To allow the Grafana dashboard to persist after the Grafana instance restarts, add the dashboard configuration JSON into a ConfigMap. ConfigMaps also allow the dashboards to be deployed with a GitOps or CD based approach. This allows the dashboard to be put under version control.

 - [Creating a Persistent Grafana Dashboard](#creating-a-persistent-grafana-dashboard)
@@ -2,9 +2,6 @@
 title: Enable Monitoring
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 As an [administrator](../authentication-permissions-and-global-configuration/manage-role-based-access-control-rbac/global-permissions.md) or [cluster owner](../authentication-permissions-and-global-configuration/manage-role-based-access-control-rbac/cluster-and-project-roles.md#cluster-roles), you can configure Rancher to deploy Prometheus to monitor your Kubernetes cluster.

 This page describes how to enable monitoring and alerting within a cluster using the new monitoring application.
@@ -2,9 +2,6 @@
 title: Configuring PrometheusRules
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 A PrometheusRule defines a group of Prometheus alerting and/or recording rules.

 > This section assumes familiarity with how monitoring components work together. For more information, see [this section.](../../../../explanations/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md)
@@ -2,7 +2,6 @@
 title: Backing up Rancher Installed with Docker
 ---

-
 After completing your Docker installation of Rancher, we recommend creating backups of it on a regular basis. Having a recent backup will let you recover quickly from an unexpected disaster.

 ## Before You Start
@@ -2,7 +2,6 @@
 title: Setting up a High-availability RKE Kubernetes Cluster
 ---

-
 This section describes how to install a Kubernetes cluster. This cluster should be dedicated to run only the Rancher server.

 > As of Rancher v2.5, Rancher can run on any Kubernetes cluster, included hosted Kubernetes solutions such as Amazon EKS. The below instructions represent only one possible way to install Kubernetes.
@@ -2,9 +2,6 @@
 title: Node Requirements for Rancher Managed Clusters
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 This page describes the requirements for the Rancher managed Kubernetes clusters where your apps and services will be installed. These downstream clusters should be separate from the three-node cluster running Rancher.

 > If Rancher is installed on a high-availability Kubernetes cluster, the Rancher server three-node cluster and downstream clusters have different requirements. For Rancher installation requirements, refer to the node requirements in the [installation section.](../../../pages-for-subheaders/installation-requirements.md)
@@ -2,9 +2,6 @@
 title: Registering Existing Clusters
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 The cluster registration feature replaced the feature to import clusters.

 The control that Rancher has to manage a registered cluster depends on the type of cluster. For details, see [Management Capabilities for Registered Clusters.](#management-capabilities-for-registered-clusters)
@@ -2,9 +2,6 @@
 title: Managing GKE Clusters
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 <Tabs>
 <TabItem value="Rancher v2.5.8+">

@@ -2,9 +2,6 @@
 title: CIS Scans
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 Rancher can run a security scan to check whether Kubernetes is deployed according to security best practices as defined in the CIS Kubernetes Benchmark.

 The `rancher-cis-benchmark` app leverages <a href="https://github.com/aquasecurity/kube-bench" target="_blank">kube-bench,</a> an open-source tool from Aqua Security, to check clusters for CIS Kubernetes Benchmark compliance. Also, to generate a cluster-wide report, the application utilizes <a href="https://github.com/vmware-tanzu/sonobuoy" target="_blank">Sonobuoy</a> for report aggregation.
@@ -2,9 +2,6 @@
 title: Enabling Experimental Features
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 Rancher includes some features that are experimental and disabled by default. You might want to enable these features, for example, if you decide that the benefits of using an [unsupported storage type](../getting-started/installation-and-upgrade/advanced-options/enable-experimental-features/unsupported-storage-drivers.md) outweighs the risk of using an untested feature. Feature flags were introduced to allow you to try these features that are not enabled by default.

 The features can be enabled in three ways:
@@ -2,9 +2,6 @@
 title: GKE Cluster Configuration Reference
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 <Tabs>
 <TabItem value="Rancher v2.5.8+">

@@ -3,9 +3,6 @@ title: Install/Upgrade Rancher on a Kubernetes Cluster
 description: Learn how to install Rancher in development and production environments. Read about single node and high availability installation
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 In this section, you'll learn how to deploy Rancher on a Kubernetes cluster using the Helm CLI.

 ## Prerequisites
@@ -3,9 +3,6 @@ title: Rancher Integration with Logging Services
 description: Rancher integrates with popular logging services. Learn the requirements and benefits of integrating with logging services, and enable logging on your cluster.
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 The [Banzai Cloud Logging operator](https://banzaicloud.com/docs/one-eye/logging-operator/) now powers Rancher's logging solution in place of the former, in-house solution.

 For an overview of the changes in v2.5, see [this section.](../explanations/integrations-in-rancher/logging/logging-architecture.md#changes-in-rancher-v25) For information about migrating from Logging V1, see [this page.](../explanations/integrations-in-rancher/logging/migrate-to-rancher-v2.5+-logging.md)
@@ -2,9 +2,6 @@
 title: Launching Kubernetes on Windows Clusters
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 When provisioning a [custom cluster](use-existing-nodes.md) using Rancher, Rancher uses RKE (the Rancher Kubernetes Engine) to install Kubernetes on your existing nodes.

 In a Windows cluster provisioned with Rancher, the cluster must contain both Linux and Windows nodes. The Kubernetes controlplane can only run on Linux nodes, and the Windows nodes can only have the worker role. Windows nodes can only be used for deploying workloads.
@@ -2,9 +2,6 @@
 title: EKS Cluster Configuration Reference
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 <Tabs>
 <TabItem value="Rancher v2.5.6+">

@@ -2,7 +2,6 @@
 title: Helm Chart Options
 ---

-
 ## Configuring Resource Limits and Requests

 The resource requests and limits can be configured when installing `rancher-monitoring`.
@@ -2,9 +2,6 @@
 title: Receiver Configuration
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 The [Alertmanager Config](https://prometheus.io/docs/alerting/latest/configuration/#configuration-file) Secret contains the configuration of an Alertmanager instance that sends out notifications based on alerts it receives from Prometheus.

 > This section assumes familiarity with how monitoring components work together. For more information about Alertmanager, see [this section.](../../explanations/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md#3-how-alertmanager-works)
@@ -2,9 +2,6 @@
 title: Route Configuration
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 The route configuration is the section of the Alertmanager custom resource that controls how the alerts fired by Prometheus are grouped and filtered before they reach the receiver.

 When a Route is changed, the Prometheus Operator regenerates the Alertmanager custom resource to reflect the changes.
@@ -2,9 +2,6 @@
 title: User Preferences
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 Each user can choose preferences to personalize their Rancher experience. To change preference settings, open the **User Settings** menu and then select **Preferences**.

 The preferences available will differ depending on whether the **User Settings** menu was accessed while on the Cluster Manager UI or the Cluster Explorer UI.
@@ -1,5 +1,3 @@
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';

 <Tabs>
 <TabItem value="Rancher v2.5.8+">
@@ -2,9 +2,6 @@
 title: Installing Rancher on a Google Kubernetes Engine Cluster
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 In this section, you'll learn how to install Rancher using Google Kubernetes Engine.

 If you already have a GKE Kubernetes cluster, skip to the step about [installing an ingress.](#7-install-an-ingress) Then install the Rancher Helm chart following the instructions on [this page.](../../../pages-for-subheaders/install-upgrade-on-a-kubernetes-cluster.md#install-the-rancher-helm-chart)
@@ -2,7 +2,6 @@
 title: Rollbacks
 ---

-
 ## Rolling Back to Rancher v2.5.0+

 To roll back to Rancher v2.5.0+, use the **Rancher Backups** application and restore Rancher from backup.
@@ -3,8 +3,6 @@ title: Port Requirements
 description: Read about port requirements needed in order for Rancher to operate properly, both for Rancher nodes and downstream Kubernetes cluster nodes
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
 import PortsIaasNodes from '@site/src/components/PortsIaasNodes'
 import PortsCustomNodes from '@site/src/components/PortsCustomNodes'
 import PortsImportedHosted from '@site/src/components/PortsImportedHosted'
@@ -2,9 +2,6 @@
 title: '1. Set up Infrastructure and Private Registry'
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 In this section, you will provision the underlying infrastructure for your Rancher management server in an air gapped environment. You will also set up the private Docker registry that must be available to your Rancher node(s).

 An air gapped environment is an environment where the Rancher server is installed offline or behind a firewall.
@@ -2,9 +2,6 @@
 title: '3. Install Kubernetes (Skip for Docker Installs)'
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 :::note

 Skip this section if you are installing Rancher on a single node with Docker.
@@ -2,9 +2,6 @@
 title: '2. Collect and Publish Images to your Private Registry'
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 This section describes how to set up your private registry so that when you install Rancher, Rancher will pull all the required images from this registry.

 By default, all images used to [provision Kubernetes clusters](../../../../pages-for-subheaders/kubernetes-clusters-in-rancher-setup.md) or launch any tools in Rancher, e.g. monitoring, pipelines, alerts, are pulled from Docker Hub. In an air gapped installation of Rancher, you will need a private registry that is located somewhere accessible by your Rancher server. Then, you will load the registry with all the images.
@@ -2,9 +2,6 @@
 title: Upgrading Rancher Installed with Docker
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 The following instructions will guide you through upgrading a Rancher server that was installed with Docker.

 :::caution
@@ -2,9 +2,6 @@
 title: Choosing a Rancher Version
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 This section describes how to choose a Rancher version.

 For a high-availability installation of Rancher, which is recommended for production, the Rancher server is installed using a **Helm chart** on a Kubernetes cluster. Refer to the [Helm version requirements](helm-version-requirements.md) to choose a version of Helm to install Rancher.
@@ -2,9 +2,6 @@
 title: Helm CLI Quick Start
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 These instructions capture a quick way to set up a proof-of-concept Rancher installation.

 These instructions assume you have a Linux virtual machine that you will communicate with from your local workstation. Rancher will be installed on the Linux machine. You will need to retrieve the IP address of that machine so that you can access Rancher from your local workstation. Rancher is designed to manage Kubernetes clusters remotely, so any Kubernetes cluster that Rancher manages in the future will also need to be able to reach this IP address.
@@ -2,9 +2,6 @@
 title: Persistent Grafana Dashboards
 ---

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 To allow the Grafana dashboard to persist after the Grafana instance restarts, add the dashboard configuration JSON into a ConfigMap. ConfigMaps also allow the dashboards to be deployed with a GitOps or CD based approach. This allows the dashboard to be put under version control.

 - [Creating a Persistent Grafana Dashboard](#creating-a-persistent-grafana-dashboard)
@@ -2,7 +2,6 @@
 title: Enable Prometheus Federator
 ---

-
 ## Requirements

 By default, Prometheus Federator is configured and intended to be deployed alongside [rancher-monitoring](https://rancher.com/docs/rancher/v2.6/en/monitoring-alerting/), which deploys Prometheus Operator alongside a Cluster Prometheus that each Project Monitoring Stack is configured to federate namespace-scoped metrics from by default.
@@ -2,7 +2,6 @@
 title: Setting up Prometheus Federator for a Workload
 ---

-
 ### Display CPU and Memory Metrics for a Workload

 Displaying CPU and memory metrics with Prometheus Federator is done the same way as with rancher-monitoring. For instructions, refer [here](../set-up-monitoring-for-workloads.md#display-cpu-and-memory-metrics-for-a-workload).
--- a/Show More
+++ b/Show More