Updating notes in Docu format

2026-09-25 12:38:05 +00:00 · 2022-07-08 11:54:36 -04:00
parent 106e84d3c0
commit 6b9095d077
13 changed files with 192 additions and 66 deletions
@@ -12,8 +12,11 @@ If you already have an AKS Kubernetes cluster, skip to the step about [installin

 # Prerequisites

->**Note**
->Deploying to Microsoft Azure will incur charges.
+:::caution
+
+Deploying to Microsoft Azure will incur charges.
+
+:::

 - [Microsoft Azure Account](https://azure.microsoft.com/en-us/free/): A Microsoft Azure Account is required to create resources for deploying Rancher and Kubernetes.
 - [Microsoft Azure Subscription](https://docs.microsoft.com/en-us/azure/cost-management-billing/manage/create-subscription#create-a-subscription-in-the-azure-portal): Use this link to follow a tutorial to create a Microsoft Azure subscription if you don't have one yet.
@@ -45,11 +45,13 @@ Deploying this Quick Start for a new virtual private cloud (VPC) and new Amazon

 In this section, you'll install an EKS cluster with an ingress by using command line tools. This guide may be useful if you want to use fewer resources while trying out Rancher on EKS.

-> **Prerequisites:**
->
-> - You should already have an AWS account.
-> - It is recommended to use an IAM user instead of the root AWS account. You will need the IAM user's access key and secret key to configure the AWS command line interface.
-> - The IAM user needs the minimum IAM policies described in the official [eksctl documentation.](https://eksctl.io/usage/minimum-iam-policies/)
+:::note Prerequisites:
+
+- You should already have an AWS account.
+- It is recommended to use an IAM user instead of the root AWS account. You will need the IAM user's access key and secret key to configure the AWS command line interface.
+- The IAM user needs the minimum IAM policies described in the official [eksctl documentation.](https://eksctl.io/usage/minimum-iam-policies/)
+
+:::

 ### 1. Prepare your Workstation

@@ -120,7 +120,11 @@ See [TLS settings]({{<baseurl>}}/rancher/v2.6/en/installation/resources/tls-sett

 By default Rancher server will detect and import the `local` cluster it's running on. User with access to the `local` cluster will essentially have "root" access to all the clusters managed by Rancher server.

-> **Important:**  If you turn addLocal off, most Rancher v2.5 features won't work, including the EKS provisioner. 
+:::caution
+
+If you turn addLocal off, most Rancher v2.5 features won't work, including the EKS provisioner. 
+
+:::

 If this is a concern in your environment you can set this option to "false" on your initial install.

@@ -181,7 +185,11 @@ We recommend configuring your load balancer as a Layer 4 balancer, forwarding pl

 You may terminate the SSL/TLS on a L7 load balancer external to the Rancher cluster (ingress). Use the `--set tls=external` option and point your load balancer at port http 80 on all of the Rancher cluster nodes. This will expose the Rancher interface on http port 80. Be aware that clients that are allowed to connect directly to the Rancher cluster will not be encrypted. If you choose to do this we recommend that you restrict direct access at the network level to just your load balancer.

-> **Note:** If you are using a Private CA signed certificate, add `--set privateCA=true` and see [Adding TLS Secrets - Using a Private CA Signed Certificate]({{<baseurl>}}/rancher/v2.6/en/installation/resources/tls-secrets/) to add the CA cert for Rancher.
+:::note
+
+If you are using a Private CA signed certificate, add `--set privateCA=true` and see [Adding TLS Secrets - Using a Private CA Signed Certificate]({{<baseurl>}}/rancher/v2.6/en/installation/resources/tls-secrets/) to add the CA cert for Rancher.
+
+:::

 Your load balancer must support long lived websocket connections and will need to insert proxy headers so Rancher can route links correctly.

@@ -217,7 +225,11 @@ Rancher will respond `200` to health checks on the `/healthz` endpoint.

 This NGINX configuration is tested on NGINX 1.14.

-> **Note:** This NGINX configuration is only an example and may not suit your environment. For complete documentation, see [NGINX Load Balancing - HTTP Load Balancing](https://docs.nginx.com/nginx/admin-guide/load-balancer/http-load-balancer/).
+:::caution
+
+This NGINX configuration is only an example and may not suit your environment. For complete documentation, see [NGINX Load Balancing - HTTP Load Balancing](https://docs.nginx.com/nginx/admin-guide/load-balancer/http-load-balancer/).
+
+:::

 - Replace `IP_NODE1`, `IP_NODE2` and `IP_NODE3` with the IP addresses of the nodes in your cluster.
 - Replace both occurrences of `FQDN` to the DNS name for Rancher.
@@ -70,7 +70,7 @@ To install `gcloud` and `kubectl`, perform the following steps:
 - Using gcloud config, to individually set your project ID, zone, and region.

 {{% tabs %}}
-{{% tab "Using gloud init" %}}
+{{% tab "Using gcloud init" %}}

 1. Run gcloud init and follow the directions:

@@ -15,10 +15,13 @@ Rancher has to be started with the lower/previous version after a rollback.

 A restore is performed by creating a Restore custom resource.

-> **Important**
->
-> * Follow the instructions from this page for restoring rancher on the same cluster where it was backed up from. In order to migrate rancher to a new cluster, follow the steps to [migrate rancher.]({{<baseurl>}}/rancher/v2.6/en/backups/migrating-rancher)
-> * While restoring Rancher on the same setup, the Rancher deployment is manually scaled down before the restore starts, then the operator will scale it back up once the restore completes. As a result, Rancher and its UI will be unavailable until the restore is complete. While the UI is unavailable, use the original cluster kubeconfig with the restore YAML file: `kubectl create -f restore.yaml`.
+:::note Important:
+
+* Follow the instructions from this page for restoring Rancher on the same cluster where it was backed up from. In order to migrate Rancher to a new cluster, follow the steps to [migrate Rancher.]({{<baseurl>}}/rancher/v2.6/en/backups/migrating-rancher)
+
+* While restoring Rancher on the same setup, the Rancher deployment is manually scaled down before the restore starts, then the operator will scale it back up once the restore completes. As a result, Rancher and its UI will be unavailable until the restore is complete. While the UI is unavailable, use the original cluster kubeconfig with the restore YAML file: `kubectl create -f restore.yaml`.
+
+:::

 ### Scale the Rancher Deployment to 0

@@ -100,7 +103,11 @@ To roll back to Rancher before v2.5, follow the procedure detailed here: [Restor

 For information on how to roll back Rancher installed with Docker, refer to [this page.]({{<baseurl>}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/single-node-rollbacks)

-> Managed clusters are authoritative for their state. This means restoring the rancher server will not revert workload deployments or changes made on managed clusters after the snapshot was taken.
+:::note
+
+Managed clusters are authoritative for their state. This means restoring the Rancher server will not revert workload deployments or changes made on managed clusters after the snapshot was taken.
+
+:::

 # Rolling Back to Rancher v2.0-v2.1

@@ -1,10 +1,14 @@
 ---
-title: Rendering the Helm Template in an Air Gapped Environment
+title: Rendering the Helm Template in an Air-Gapped Environment
 shortTitle: Air Gap Upgrade
 weight: 1
 ---

-> These instructions assume you have already followed the instructions for a Kubernetes upgrade on [this page,]({{<baseurl>}}/rancher/v2.6/en/installation/install-rancher-on-k8s/upgrades/) including the prerequisites, up until step 3. Upgrade Rancher.
+:::note
+
+These instructions assume you have already followed the instructions for a Kubernetes upgrade on [this page,]({{<baseurl>}}/rancher/v2.6/en/installation/install-rancher-on-k8s/upgrades/) including the prerequisites, up until step 3. Upgrade Rancher.
+
+:::

 ### Rancher Helm Template Options

@@ -74,9 +78,13 @@ kubectl -n cattle-system apply -R -f ./rancher

 Log into Rancher to confirm that the upgrade succeeded.

->**Having network issues following upgrade?**
->
-> See [Restoring Cluster Networking]({{<baseurl>}}/rancher/v2.0-v2.4/en/installation/install-rancher-on-k8s/upgrades/namespace-migration).
+:::tip
+
+Having network issues following upgrade?
+
+See [Restoring Cluster Networking]({{<baseurl>}}/rancher/v2.0-v2.4/en/installation/install-rancher-on-k8s/upgrades/namespace-migration).
+
+:::

 # Known Upgrade Issues

@@ -84,8 +84,11 @@ You'll use the backup as a restore point if something goes wrong during upgrade.
    rancher-<CHART_REPO>	 https://releases.rancher.com/server-charts/<CHART_REPO>
    ```

-    > **Note:** If you want to switch to a different Helm chart repository, please follow the [steps on how to switch repositories]({{<baseurl>}}/rancher/v2.6/en/installation/resources/choosing-version/#switching-to-a-different-helm-chart-repository). If you switch repositories, make sure to list the repositories again before continuing onto Step 3 to ensure you have the correct one added.
+    :::note
+    
+    If you want to switch to a different Helm chart repository, please follow the [steps on how to switch repositories]({{<baseurl>}}/rancher/v2.6/en/installation/resources/choosing-version/#switching-to-a-different-helm-chart-repository). If you switch repositories, make sure to list the repositories again before continuing onto Step 3 to ensure you have the correct one added.

+    :::

 1. Fetch the latest chart to install Rancher from the Helm chart repository.

@@ -104,7 +107,11 @@ You'll use the backup as a restore point if something goes wrong during upgrade.

 This section describes how to upgrade normal (Internet-connected) or air gap installations of Rancher with Helm.

-> **Air Gap Instructions:** If you are installing Rancher in an air gapped environment, skip the rest of this page and render the Helm template by following the instructions on [this page.](./air-gap-upgrade)
+:::note Air Gap Instructions:
+
+If you are installing Rancher in an air gapped environment, skip the rest of this page and render the Helm template by following the instructions on [this page.](./air-gap-upgrade)
+
+:::


 Get the values, which were passed with `--set`, from the current Rancher Helm chart that is installed.
@@ -115,7 +122,12 @@ helm get values rancher -n cattle-system
 hostname: rancher.my.org
 ```

-> **Note:** There will be more values that are listed with this command. This is just an example of one of the values.
+:::note
+
+There will be more values that are listed with this command. This is just an example of one of the values.
+
+:::
+

 If you are also upgrading cert-manager to the latest version from a version older than 0.11.0, follow [Option B: Reinstalling Rancher and cert-manager.](#option-b-reinstalling-rancher-and-cert-manager)

@@ -133,7 +145,11 @@ helm upgrade rancher rancher-<CHART_REPO>/rancher \
  --set hostname=rancher.my.org
 ```

-> **Note:** The above is an example, there may be more values from the previous step that need to be appended.
+:::note
+
+The above is an example, there may be more values from the previous step that need to be appended.
+
+:::

 Alternatively, it's possible to export the current values to a file and reference that file during upgrade. For example, to only change the Rancher version:

@@ -176,9 +192,13 @@ If you are currently running the cert-manager whose version is 1.5 or below, and

 Log into Rancher to confirm that the upgrade succeeded.

->**Having network issues following upgrade?**
->
-> See [Restoring Cluster Networking]({{<baseurl>}}/rancher/v2.0-v2.4/en/installation/install-rancher-on-k8s/upgrades/namespace-migration).
+:::tip
+
+Having network issues following upgrade?
+
+See [Restoring Cluster Networking]({{<baseurl>}}/rancher/v2.0-v2.4/en/installation/install-rancher-on-k8s/upgrades/namespace-migration).
+
+:::

 # Known Upgrade Issues

@@ -1,5 +1,5 @@
 ---
-title: Air Gapped Helm CLI Install
+title: Air-Gapped Helm CLI Install
 weight: 1
 ---

@@ -11,7 +11,11 @@ For more information on each installation option, refer to [this page.]({{<baseu

 Throughout the installation instructions, there will be _tabs_ for each installation option.

-> **Important:** If you install Rancher following the Docker installation guide, there is no upgrade path to transition your Docker Installation to a Kubernetes Installation.
+:::note Important:
+
+If you install Rancher following the Docker installation guide, there is no upgrade path to transition your Docker Installation to a Kubernetes Installation.
+
+:::

 # Installation Outline

@@ -16,10 +16,14 @@ For security purposes, SSL (Secure Sockets Layer) is required when using Rancher
 | `CATTLE_SYSTEM_DEFAULT_REGISTRY` | `<REGISTRY.YOURDOMAIN.COM:PORT>` | Configure Rancher server to always pull from your private registry when provisioning clusters.  |
 | `CATTLE_SYSTEM_CATALOG`          | `bundled`                        | Configure Rancher server to use the packaged copy of Helm system charts. 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. These [Helm charts](https://github.com/rancher/system-charts) are located in GitHub, but since you are in an air gapped environment, using the charts that are bundled within Rancher is much easier than setting up a Git mirror. |

-> **Do you want to..**.
->
-> - Configure custom CA root certificate to access your services? See [Custom CA root certificate]({{<baseurl>}}/rancher/v2.6/en/installation/resources/custom-ca-root-certificate/).
-> - Record all transactions with the Rancher API? See [API Auditing]({{<baseurl>}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/advanced/#api-audit-log).
+:::note
+
+**Do you want to..**
+
+- Configure custom CA root certificate to access your services? See [Custom CA root certificate]({{<baseurl>}}/rancher/v2.6/en/installation/resources/custom-ca-root-certificate/).
+- Record all transactions with the Rancher API? See [API Auditing]({{<baseurl>}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/advanced/#api-audit-log).
+
+:::

 Choose from the following options:

@@ -55,11 +59,14 @@ docker run -d --restart=unless-stopped \

 In development or testing environments where your team will access your Rancher server, create a self-signed certificate for use with your install so that your team can verify they're connecting to your instance of Rancher.

-> **Prerequisites:**
-> From a computer with an internet connection, create a self-signed certificate using [OpenSSL](https://www.openssl.org/) or another method of your choice.
->
-> - The certificate files must be in PEM format.
-> - In your certificate file, include all intermediate certificates in the chain. Order your certificates with your certificate first, followed by the intermediates. For an example, see [Certificate Troubleshooting.]({{<baseurl>}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/troubleshooting)
+:::note Prerequisites:
+
+From a computer with an internet connection, create a self-signed certificate using [OpenSSL](https://www.openssl.org/) or another method of your choice.
+
+- The certificate files must be in PEM format.
+- In your certificate file, include all intermediate certificates in the chain. Order your certificates with your certificate first, followed by the intermediates. For an example, see [Certificate Troubleshooting.]({{<baseurl>}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/troubleshooting)
+
+:::

 After creating your certificate, log into your Linux host, and then run the installation command below. When entering the command, use the table below to replace each placeholder. Use the `-v` flag and provide the path to your certificates to mount them in your container.

@@ -94,7 +101,11 @@ docker run -d --restart=unless-stopped \

 In development or testing environments where you're exposing an app publicly, use a certificate signed by a recognized CA so that your user base doesn't encounter security warnings.

-> **Prerequisite:** The certificate files must be in PEM format.
+:::note Prerequisite:
+
+The certificate files must be in PEM format.
+
+:::

 After obtaining your certificate, log into your Linux host, and then run the installation command below. When entering the command, use the table below to replace each placeholder. Because your certificate is signed by a recognized CA, mounting an additional CA certificate file is unnecessary.

@@ -106,7 +117,11 @@ After obtaining your certificate, log into your Linux host, and then run the ins
 | `<REGISTRY.YOURDOMAIN.COM:PORT>` | Your private registry URL and port.                                                                                           |
 | `<RANCHER_VERSION_TAG>`          | The release tag of the [Rancher version]({{<baseurl>}}/rancher/v2.6/en/installation/resources/chart-options/) that you want to install. |

-> **Note:** Use the `--no-cacerts` as argument to the container to disable the default CA certificate generated by Rancher.
+:::note
+
+Use the `--no-cacerts` as argument to the container to disable the default CA certificate generated by Rancher.
+
+:::

 Privileged access is [required.](#privileged-access-for-rancher)

@@ -126,5 +141,9 @@ docker run -d --restart=unless-stopped \



-> **Note:** If you don't intend to send telemetry data, opt out [telemetry]({{<baseurl>}}/rancher/v2.6/en/faq/telemetry/) during the initial login.
+:::note
+
+If you don't intend to send telemetry data, opt out [telemetry]({{<baseurl>}}/rancher/v2.6/en/faq/telemetry/) during the initial login.
+
+:::

@@ -52,7 +52,11 @@ Rancher Server is designed to be secure by default and requires SSL/TLS configur

 When Rancher is installed on an air gapped Kubernetes cluster, there are two recommended options for the source of the certificate.

-> **Note:** If you want terminate SSL/TLS externally, see [TLS termination on an External Load Balancer]({{<baseurl>}}/rancher/v2.6/en/installation/install-rancher-on-k8s/chart-options/#external-tls-termination).
+:::note
+
+If you want terminate SSL/TLS externally, see [TLS termination on an External Load Balancer]({{<baseurl>}}/rancher/v2.6/en/installation/install-rancher-on-k8s/chart-options/#external-tls-termination).
+
+:::

 | Configuration                              | Chart option                 | Description                                                                                                                                                 | Requires cert-manager |
 | ------------------------------------------ | ---------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------- |
@@ -78,8 +82,11 @@ Based on the choice your made in [2. Choose your SSL Configuration](#2-choose-yo

 By default, Rancher generates a CA and uses cert-manager to issue the certificate for access to the Rancher server interface.

-> **Note:**
-> Recent changes to cert-manager require an upgrade. If you are upgrading Rancher and using a version of cert-manager older than v0.11.0, please see our [upgrade cert-manager documentation]({{<baseurl>}}/rancher/v2.6/en/installation/resources/upgrading-cert-manager/).
+:::note
+
+Recent changes to cert-manager require an upgrade. If you are upgrading Rancher and using a version of cert-manager older than v0.11.0, please see our [upgrade cert-manager documentation]({{<baseurl>}}/rancher/v2.6/en/installation/resources/upgrading-cert-manager/).
+
+:::

 ### 1. Add the cert-manager repo

@@ -233,7 +240,11 @@ kubectl -n cattle-system apply -R -f ./rancher
 ```
 The installation is complete.

-> **Note:** If you don't intend to send telemetry data, opt out [telemetry]({{<baseurl>}}/rancher/v2.6/en/faq/telemetry/) during the initial login. Leaving this active in an air-gapped environment can cause issues if the sockets cannot be opened successfully.
+:::caution
+
+If you don't intend to send telemetry data, opt out [telemetry]({{<baseurl>}}/rancher/v2.6/en/faq/telemetry/) during the initial login. Leaving this active in an air-gapped environment can cause issues if the sockets cannot be opened successfully.
+
+:::

 # Additional Resources

@@ -3,7 +3,11 @@ title: '3. Install Kubernetes (Skip for Docker Installs)'
 weight: 300
 ---

-> Skip this section if you are installing Rancher on a single node with Docker.
+:::note
+
+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.]({{<baseurl>}}/rancher/v2.6/en/overview/architecture-recommendations/#environment-for-kubernetes-installations) This cluster should be dedicated to run only the Rancher server.

@@ -86,7 +90,11 @@ INSTALL_K3S_SKIP_DOWNLOAD=true K3S_URL=https://myserver:6443 K3S_TOKEN=mynodetok
 Note, take care to ensure you replace `myserver` with the IP or valid DNS of the server and replace `mynodetoken` with the node-token from the server.
 The node-token is on the server at `/var/lib/rancher/k3s/server/node-token`

->**Note:** K3s additionally provides a `--resolv-conf` flag for kubelets, which may help with configuring DNS in air-gap networks.
+:::note
+
+K3s additionally provides a `--resolv-conf` flag for kubelets, which may help with configuring DNS in air-gapped networks.
+
+:::

 ### 4. Save and Start Using the kubeconfig File

@@ -151,7 +159,11 @@ This file is an RKE configuration file, which is a configuration for the cluster

 Replace values in the code sample below with help of the _RKE Options_ table. Use the IP address or DNS names of the three nodes you created.

-> **Tip:** For more details on the options available, see the RKE [Config Options]({{<baseurl>}}/rke/latest/en/config-options/).
+:::tip
+
+For more details on the options available, see the RKE [Config Options]({{<baseurl>}}/rke/latest/en/config-options/).
+
+:::

 <figcaption>RKE Options</figcaption>

@@ -200,8 +212,11 @@ rke up --config ./rancher-cluster.yml

 ### 4. Save Your Files

-> **Important**
-> The files mentioned below are needed to maintain, troubleshoot and upgrade your cluster.
+:::note Important:
+
+The files mentioned below are needed to maintain, troubleshoot, and upgrade your cluster.
+
+:::

 Save a copy of the following files in a secure location:

@@ -211,7 +226,11 @@ Save a copy of the following files in a secure location:
 {{% /tab %}}
 {{% /tabs %}}

-> **Note:** The "rancher-cluster" parts of the two latter file names are dependent on how you name the RKE cluster configuration file.
+:::note
+
+The "rancher-cluster" parts of the two latter file names are dependent on how you name the RKE cluster configuration file.
+
+:::

 ### Issues or errors?

@@ -11,11 +11,13 @@ Populating the private registry with images is the same process for installing R

 The steps in this section differ depending on whether or not you are planning to use Rancher to provision a downstream cluster with Windows nodes or not. By default, we provide the steps of how to populate your private registry assuming that Rancher will provision downstream Kubernetes clusters with only Linux nodes. But if you plan on provisioning any [downstream Kubernetes clusters using Windows nodes]({{<baseurl>}}/rancher/v2.6/en/cluster-provisioning/rke-clusters/windows-clusters/), there are separate instructions to support the images needed.

-> **Prerequisites:**
->
-> You must have a [private registry](https://docs.docker.com/registry/deploying/#run-an-externally-accessible-registry) available to use.
->
-> If the registry has certs, follow [this K3s documentation](https://rancher.com/docs/k3s/latest/en/installation/private-registry/) about adding a private registry. The certs and registry configuration files need to be mounted into the Rancher container.
+:::note Prerequisites:
+
+You must have a [private registry](https://docs.docker.com/registry/deploying/#run-an-externally-accessible-registry) available to use.
+
+If the registry has certs, follow [this K3s documentation](https://rancher.com/docs/k3s/latest/en/installation/private-registry/) about adding a private registry. The certs and registry configuration files need to be mounted into the Rancher container.
+
+:::

 {{% tabs %}}
 {{% tab "Linux Only Clusters" %}}
@@ -47,7 +49,11 @@ If you will use ARM64 hosts, the registry must support manifests. As of April 20

 ### 2. Collect the cert-manager image

-> Skip this step if you are using your own certificates, or if you are terminating TLS on an external load balancer.
+:::note
+
+Skip this step if you are using your own certificates, or if you are terminating TLS on an external load balancer.
+
+:::

 In a Kubernetes Install, if you elect to use the Rancher default self-signed TLS certificates, you must add the [`cert-manager`](https://hub.helm.sh/charts/jetstack/cert-manager) image to `rancher-images.txt` as well. 

@@ -55,7 +61,11 @@ In a Kubernetes Install, if you elect to use the Rancher default self-signed TLS

 1.  Fetch the latest `cert-manager` Helm chart and parse the template for image details:

-    > **Note:** Recent changes to cert-manager require an upgrade. If you are upgrading Rancher and using a version of cert-manager older than v0.12.0, please see our [upgrade documentation]({{<baseurl>}}/rancher/v2.6/en/installation/resources/upgrading-cert-manager/).
+    :::note
+    
+    Recent changes to cert-manager require an upgrade. If you are upgrading Rancher and using a version of cert-manager older than v0.12.0, please see our [upgrade documentation]({{<baseurl>}}/rancher/v2.6/en/installation/resources/upgrading-cert-manager/).
+
+    :::

    ```plain
    helm repo add jetstack https://charts.jetstack.io
@@ -62,8 +62,11 @@ For an example showing how to set up an NGINX load balancer, refer to [this page

 For a how-to guide for setting up an Amazon ELB Network Load Balancer, refer to [this page.]({{<baseurl>}}/rancher/v2.6/en/installation/resources/k8s-tutorials/infrastructure-tutorials/nlb/)

-> **Important:**
-> Do not use this load balancer (i.e, the `local` cluster Ingress) to load balance applications other than Rancher following installation. Sharing this Ingress with other applications may result in websocket errors to Rancher following Ingress configuration reloads for other apps. We recommend dedicating the `local` cluster to Rancher and no other applications.
+:::note Important:
+
+Do not use this load balancer (i.e, the `local` cluster Ingress) to load balance applications other than Rancher following installation. Sharing this Ingress with other applications may result in websocket errors to Rancher following Ingress configuration reloads for other apps. We recommend dedicating the `local` cluster to Rancher and no other applications.
+
+:::

 ### 4. Set up the DNS Record

@@ -125,8 +128,11 @@ For an example showing how to set up an NGINX load balancer, refer to [this page

 For a how-to guide for setting up an Amazon ELB Network Load Balancer, refer to [this page.]({{<baseurl>}}/rancher/v2.6/en/installation/resources/k8s-tutorials/infrastructure-tutorials/nlb/)

-> **Important:**
-> Do not use this load balancer (i.e, the `local` cluster Ingress) to load balance applications other than Rancher following installation. Sharing this Ingress with other applications may result in websocket errors to Rancher following Ingress configuration reloads for other apps. We recommend dedicating the `local` cluster to Rancher and no other applications.
+:::caution
+
+Do not use this load balancer (i.e, the `local` cluster Ingress) to load balance applications other than Rancher following installation. Sharing this Ingress with other applications may result in websocket errors to Rancher following Ingress configuration reloads for other apps. We recommend dedicating the `local` cluster to Rancher and no other applications.
+
+:::

 ### 3. Set up the DNS Record

@@ -148,9 +154,14 @@ If you need help with creating a private registry, please refer to the [official

 {{% /tab %}}
 {{% tab "Docker" %}}
-> The Docker installation is for Rancher users that are wanting to test out Rancher. Since there is only one node and a single Docker container, if the node goes down, you will lose all the data of your Rancher server.
->
-> The Rancher backup operator can be used to migrate Rancher from the single Docker container install to an installation on a high-availability Kubernetes cluster. For details, refer to the documentation on [migrating Rancher to a new cluster.]({{<baseurl>}}/rancher/v2.6/en/backups/migrating-rancher)
+
+:::note Notes:
+
+- The Docker installation is for Rancher users that are wanting to test out Rancher. Since there is only one node and a single Docker container, if the node goes down, you will lose all the data of your Rancher server.
+
+- The Rancher backup operator can be used to migrate Rancher from the single Docker container install to an installation on a high-availability Kubernetes cluster. For details, refer to the documentation on [migrating Rancher to a new cluster.]({{<baseurl>}}/rancher/v2.6/en/backups/migrating-rancher)
+
+:::

 ### 1. Set up a Linux Node