Merge release/v2.8.8 into main (#1479 )

* 2.8.8 versions table entry * 2.8.8 webhook table entry * 2.8.8 csp adapter entry * 2.8.8 deprecated features entry
Merge release/v2.9.2 into main (#1482 )
2026-09-29 22:49:17 +00:00 · 2024-09-20 12:39:28 -04:00 · 2024-09-20 12:39:10 -04:00 · 2024-09-19 13:01:47 -07:00 · 2024-09-19 12:05:51 -07:00 · 2024-09-19 11:41:34 -07:00
857 changed files with 4411 additions and 15759 deletions
@@ -0,0 +1,8 @@
 version: 2
 updates:
  - package-ecosystem: gitsubmodule
    schedule:
        interval: "daily"
    directory: /
@@ -4,6 +4,8 @@ on:
  push:
    branches:
      - main
    paths-ignore:
      - '**/README.md'
 jobs:
  build:
@@ -2,8 +2,8 @@ name: Test deployment
 on:
  pull_request:
-    branches:
+    paths-ignore:
-      - main
+      - '**/README.md'
 jobs:
  test-deploy:
@@ -5,7 +5,10 @@
 # It uses Vale (https://vale.sh/docs/vale-cli/installation/) to provide feedback base off the SUSE Style Guide / OpenSUSE style rules (https://github.com/openSUSE/suse-vale-styleguide)
 name: Style check
-on: [pull_request]
+on:
  pull_request:
    paths-ignore:
      - '**/README.md'
 jobs:
  vale-lint:
@@ -1,7 +1,7 @@
-StylesPath = .github/styles
+StylesPath = .github/styles/suse-vale-styleguide
 [formtats]
 mdx = md
 [*.md]
-BasedOnStyles = suse-vale-styleguide
+BasedOnStyles = common
@@ -15,9 +15,9 @@ To get started, [fork](https://github.com/rancher/rancher-docs/fork) and clone t
 Our repository doesn't allow you to make changes directly to the `main` branch. Create a working branch and make pull requests from your fork to [rancher/rancher-docs](https://github.com/rancher/rancher-docs).
-For most updates, you'll need to edit a file in the `/docs` directory, which represents the ["Latest"](https://ranchermanager.docs.rancher.com/) version of our published documentation. The "Latest" version is a mirror of the most recently released version of Rancher. As of December 2023, the most recently released version of Rancher is 2.8.
+For most updates, you'll need to edit a file in the `/docs` directory, which represents the ["Latest"](https://ranchermanager.docs.rancher.com/) version of our published documentation. The "Latest" version is a mirror of the most recently released version of Rancher. As of August 2024, the most recently released version of Rancher is 2.9.
-Whenever an update is made to `/docs`, you should apply the same change to the corresponding file in `/versioned_docs/version-2.8`. If a change only affects older versions, you don't need to mirror it to the `/docs` directory.
+Whenever an update is made to `/docs`, you should apply the same change to the corresponding file in `/versioned_docs/version-2.9`. If a change only affects older versions, you don't need to mirror it to the `/docs` directory.
 If a file is moved or renamed, you'll also need to edit the `sidebars.js` files for each affected version, as well as the list of redirects in `docusaurus.config.js`. See [Moving or Renaming Docs](./moving-or-renaming-docs.md).
@@ -1,5 +1,6 @@
 ---
 title: API Reference
 hide_table_of_contents: true
 ---
 <head>
@@ -6,18 +6,20 @@ title: Deprecated Features in Rancher
  <link rel="canonical" href="https://ranchermanager.docs.rancher.com/faq/deprecated-features"/>
 </head>
-### What is Rancher's deprecation policy?
+## What is Rancher's deprecation policy?
 We have published our official deprecation policy in the support [terms of service](https://rancher.com/support-maintenance-terms).
-### Where can I find out which features have been deprecated in Rancher?
+## Where can I find out which features have been deprecated in Rancher?
 Rancher will publish deprecated features as part of the [release notes](https://github.com/rancher/rancher/releases) for Rancher found on GitHub. Please consult the following patch releases for deprecated features:
 | Patch Version |  Release Date |
 |---------------|---------------|
-| [2.9.0](https://github.com/rancher/rancher/releases/tag/v2.9.0) | July 31, 2024 |
+| [2.9.2](https://github.com/rancher/rancher/releases/tag/v2.9.2) | Sep 19, 2024 |
 | [2.9.1](https://github.com/rancher/rancher/releases/tag/v2.9.1) | Aug 26, 2024 |
 | [2.9.0](https://github.com/rancher/rancher/releases/tag/v2.9.0) | Jul 31, 2024 |
-### What can I expect when a feature is marked for deprecation?
+## What can I expect when a feature is marked for deprecation?
 In the release where functionality is marked as "Deprecated", it will still be available and supported allowing upgrades to follow the usual procedure. Once upgraded, users/admins should start planning to move away from the deprecated functionality before upgrading to the release it marked as removed. The recommendation for new deployments is to not use the deprecated feature.
@@ -18,7 +18,7 @@ enable_cri_dockerd: true
 For users looking to use another container runtime, Rancher has the edge-focused K3s and datacenter-focused RKE2 Kubernetes distributions that use containerd as the default runtime. Imported RKE2 and K3s Kubernetes clusters can then be upgraded and managed through Rancher even after the removal of in-tree Dockershim in Kubernetes 1.24.
-### FAQ
+## FAQ
 <br/>
@@ -8,11 +8,11 @@ title: Installing and Configuring kubectl
 `kubectl` is a CLI utility for running commands against Kubernetes clusters. It's required for many maintenance and administrative tasks in Rancher 2.x.
-### Installation
+## Installation
 See [kubectl Installation](https://kubernetes.io/docs/tasks/tools/install-kubectl/) for installation on your operating system.
-### Configuration
+## Configuration
 When you create a Kubernetes cluster with RKE, RKE creates a `kube_config_cluster.yml` in the local directory that contains credentials to connect to your new cluster with tools like `kubectl` or `helm`.
@@ -9,11 +9,11 @@ title: Rancher is No Longer Needed
 This page is intended to answer questions about what happens if you don't want Rancher anymore, if you don't want a cluster to be managed by Rancher anymore, or if the Rancher server is deleted.
-### If the Rancher server is deleted, what happens to the workloads in my downstream clusters?
+## If the Rancher server is deleted, what happens to the workloads in my downstream clusters?
 If Rancher is ever deleted or unrecoverable, all workloads in the downstream Kubernetes clusters managed by Rancher will continue to function as normal.
-### If the Rancher server is deleted, how do I access my downstream clusters?
+## If the Rancher server is deleted, how do I access my downstream clusters?
 The capability to access a downstream cluster without Rancher depends on the type of cluster and the way that the cluster was created. To summarize:
@@ -21,7 +21,7 @@ The capability to access a downstream cluster without Rancher depends on the typ
 - **Hosted Kubernetes clusters:** If you created the cluster in a cloud-hosted Kubernetes provider such as EKS, GKE, or AKS, you can continue to manage the cluster using your provider's cloud credentials.
 - **RKE clusters:** To access an [RKE cluster,](../how-to-guides/new-user-guides/launch-kubernetes-with-rancher/launch-kubernetes-with-rancher.md) the cluster must have the [authorized cluster endpoint](../reference-guides/rancher-manager-architecture/communicating-with-downstream-user-clusters.md#4-authorized-cluster-endpoint) enabled, and you must have already downloaded the cluster's kubeconfig file from the Rancher UI. (The authorized cluster endpoint is enabled by default for RKE clusters.) With this endpoint, you can access your cluster with kubectl directly instead of communicating through the Rancher server's [authentication proxy.](../reference-guides/rancher-manager-architecture/communicating-with-downstream-user-clusters.md#1-the-authentication-proxy) For instructions on how to configure kubectl to use the authorized cluster endpoint, refer to the section about directly accessing clusters with [kubectl and the kubeconfig file.](../how-to-guides/new-user-guides/manage-clusters/access-clusters/use-kubectl-and-kubeconfig.md#authenticating-directly-with-a-downstream-cluster) These clusters will use a snapshot of the authentication as it was configured when Rancher was removed.
-### What if I don't want Rancher anymore?
+## What if I don't want Rancher anymore?
 :::note
@@ -44,7 +44,7 @@ If you installed Rancher with Docker, you can uninstall Rancher by removing the
 Imported clusters will not be affected by Rancher being removed. For other types of clusters, refer to the section on [accessing downstream clusters when Rancher is removed.](#if-the-rancher-server-is-deleted-how-do-i-access-my-downstream-clusters)
-### What if I don't want my registered cluster managed by Rancher?
+## What if I don't want my registered cluster managed by Rancher?
 If a registered cluster is deleted from the Rancher UI, the cluster is detached from Rancher, leaving it intact and accessible by the same methods that were used to access it before it was registered in Rancher.
@@ -56,7 +56,7 @@ To detach the cluster,
 **Result:** The registered cluster is detached from Rancher and functions normally outside of Rancher.
-### What if I don't want my RKE cluster or hosted Kubernetes cluster managed by Rancher?
+## What if I don't want my RKE cluster or hosted Kubernetes cluster managed by Rancher?
 At this time, there is no functionality to detach these clusters from Rancher. In this context, "detach" is defined as the ability to remove Rancher components from the cluster and manage access to the cluster independently of Rancher.
@@ -1,21 +1,20 @@
 ---
 title: Security FAQ
 ---
 <head>
  <link rel="canonical" href="https://ranchermanager.docs.rancher.com/faq/security"/>
 </head>
-### Is there a Hardening Guide?
+## Is there a Hardening Guide?
 The Hardening Guide is located in the main [Security](../reference-guides/rancher-security/rancher-security.md) section.
-### Have hardened Rancher Kubernetes clusters been evaluated by the CIS Kubernetes Benchmark? Where can I find the results?
+## Have hardened Rancher Kubernetes clusters been evaluated by the CIS Kubernetes Benchmark? Where can I find the results?
 We have run the CIS Kubernetes benchmark against a hardened Rancher Kubernetes cluster.  The results of that assessment can be found in the main [Security](../reference-guides/rancher-security/rancher-security.md) section.
-### How does Rancher verify communication with downstream clusters, and what are some associated security concerns?
+## How does Rancher verify communication with downstream clusters, and what are some associated security concerns?
 Communication between the Rancher server and downstream clusters is performed through agents. Rancher uses either a registered certificate authority (CA) bundle or the local trust store to verify communication between Rancher agents and the Rancher server. Using a CA bundle for verification is more strict, as only the certificates based on that bundle are trusted. If TLS verification for a explicit CA bundle fails, Rancher may fall back to using the local trust store for verifying future communication. Any CA within the local trust store can then be used to generate a valid certificate.
@@ -6,9 +6,10 @@ title: Technical FAQ
  <link rel="canonical" href="https://ranchermanager.docs.rancher.com/faq/technical-items"/>
 </head>
-### How can I reset the administrator password?
+## How can I reset the administrator password?
 Docker install:
 Docker Install:
 ```
 $ docker exec -ti <container_id> reset-password
 New password for default administrator (user-xxxxx):
@@ -16,6 +17,7 @@ New password for default administrator (user-xxxxx):
 ```
 Kubernetes install (Helm):
 ```
 $ KUBECONFIG=./kube_config_cluster.yml
 $ kubectl --kubeconfig $KUBECONFIG -n cattle-system exec $(kubectl --kubeconfig $KUBECONFIG -n cattle-system get pods -l app=rancher --no-headers | head -1 | awk '{ print $1 }') -c rancher -- reset-password
@@ -23,10 +25,10 @@ New password for default administrator (user-xxxxx):
 <new_password>
 ```
 ## I deleted/deactivated the last admin, how can I fix it?
 Docker install:
 ### I deleted/deactivated the last admin, how can I fix it?
 Docker Install:
 ```
 $ docker exec -ti <container_id> ensure-default-admin
 New default administrator (user-xxxxx)
@@ -35,38 +37,40 @@ New password for default administrator (user-xxxxx):
 ```
 Kubernetes install (Helm):
 ```
 $ KUBECONFIG=./kube_config_cluster.yml
 $ kubectl --kubeconfig $KUBECONFIG -n cattle-system exec $(kubectl --kubeconfig $KUBECONFIG -n cattle-system get pods -l app=rancher | grep '1/1' | head -1 | awk '{ print $1 }') -- ensure-default-admin
 New password for default administrator (user-xxxxx):
 <new_password>
 ```
-### How can I enable debug logging?
+
 ## How can I enable debug logging?
 See [Troubleshooting: Logging](../troubleshooting/other-troubleshooting-tips/logging.md)
-### My ClusterIP does not respond to ping
+## My ClusterIP does not respond to ping
 ClusterIP is a virtual IP, which will not respond to ping. Best way to test if the ClusterIP is configured correctly, is by using `curl` to access the IP and port to see if it responds.
-### Where can I manage Node Templates?
+## Where can I manage Node Templates?
 Node Templates can be accessed by opening your account menu (top right) and selecting `Node Templates`.
-### Why is my Layer-4 Load Balancer in `Pending` state?
+## Why is my Layer-4 Load Balancer in `Pending` state?
 The Layer-4 Load Balancer is created as `type: LoadBalancer`. In Kubernetes, this needs a cloud provider or controller that can satisfy these requests, otherwise these will be in `Pending` state forever. More information can be found on [Cloud Providers](../how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-cloud-providers/set-up-cloud-providers.md) or [Create External Load Balancer](https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/)
-### Where is the state of Rancher stored?
+## Where is the state of Rancher stored?
 - Docker Install: in the embedded etcd of the `rancher/rancher` container, located at `/var/lib/rancher`.
 - Kubernetes install: in the etcd of the RKE cluster created to run Rancher.
-### How are the supported Docker versions determined?
+## How are the supported Docker versions determined?
 We follow the validated Docker versions for upstream Kubernetes releases. The validated versions can be found under [External Dependencies](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.10.md#external-dependencies) in the Kubernetes release CHANGELOG.md.
-### How can I access nodes created by Rancher?
+## How can I access nodes created by Rancher?
 SSH keys to access the nodes created by Rancher can be downloaded via the **Nodes** view. Choose the node which you want to access and click on the vertical ⋮ button at the end of the row, and choose **Download Keys** as shown in the picture below.
@@ -78,14 +82,14 @@ Unzip the downloaded zip file, and use the file `id_rsa` to connect to you host.
 $ ssh -i id_rsa user@ip_of_node
 ```
-### How can I automate task X in Rancher?
+## How can I automate task X in Rancher?
 The UI consists of static files, and works based on responses of the API. That means every action/task that you can execute in the UI, can be automated via the API. There are 2 ways to do this:
 * Visit `https://your_rancher_ip/v3` and browse the API options.
 * Capture the API calls when using the UI (Most commonly used for this is [Chrome Developer Tools](https://developers.google.com/web/tools/chrome-devtools/#network) but you can use anything you like)
-### The IP address of a node changed, how can I recover?
+## The IP address of a node changed, how can I recover?
 A node is required to have a static IP configured (or a reserved IP via DHCP). If the IP of a node has changed, you will have to remove it from the cluster and readd it. After it is removed, Rancher will update the cluster to the correct state. If the cluster is no longer in `Provisioning` state, the node is removed from the cluster.
@@ -93,11 +97,11 @@ When the IP address of the node changed, Rancher lost connection to the node, so
 When the node is removed from the cluster, and the node is cleaned, you can readd the node to the cluster.
-### How can I add more arguments/binds/environment variables to Kubernetes components in a Rancher Launched Kubernetes cluster?
+## How can I add more arguments/binds/environment variables to Kubernetes components in a Rancher Launched Kubernetes cluster?
 You can add more arguments/binds/environment variables via the [Config File](../reference-guides/cluster-configuration/rancher-server-configuration/rke1-cluster-configuration.md#rke-cluster-config-file-reference) option in Cluster Options. For more information, see the [Extra Args, Extra Binds, and Extra Environment Variables](https://rancher.com/docs/rke/latest/en/config-options/services/services-extras/) in the RKE documentation or browse the [Example Cluster.ymls](https://rancher.com/docs/rke/latest/en/example-yamls/).
-### How do I check if my certificate chain is valid?
+## How do I check if my certificate chain is valid?
 Use the `openssl verify` command to validate your certificate chain:
@@ -138,7 +142,7 @@ subject= /C=GB/ST=England/O=Alice Ltd/CN=rancher.yourdomain.com
 issuer= /C=GB/ST=England/O=Alice Ltd/CN=Alice Intermediate CA
 ```
-### How do I check `Common Name` and `Subject Alternative Names` in my server certificate?
+## How do I check `Common Name` and `Subject Alternative Names` in my server certificate?
 Although technically an entry in `Subject Alternative Names` is required, having the hostname in both `Common Name` and as entry in `Subject Alternative Names` gives you maximum compatibility with older browser/applications.
@@ -156,7 +160,7 @@ openssl x509 -noout -in cert.pem -text | grep DNS
                DNS:rancher.my.org
 ```
-### Why does it take 5+ minutes for a pod to be rescheduled when a node has failed?
+## Why does it take 5+ minutes for a pod to be rescheduled when a node has failed?
 This is due to a combination of the following default Kubernetes settings:
@@ -175,6 +179,6 @@ In Kubernetes v1.13, the `TaintBasedEvictions` feature is enabled by default. Se
  * `default-not-ready-toleration-seconds`: Indicates the tolerationSeconds of the toleration for notReady:NoExecute that is added by default to every pod that does not already have such a toleration.
  * `default-unreachable-toleration-seconds`: Indicates the tolerationSeconds of the toleration for unreachable:NoExecute that is added by default to every pod that does not already have such a toleration.
-### Can I use keyboard shortcuts in the UI?
+## Can I use keyboard shortcuts in the UI?
 Yes, most parts of the UI can be reached using keyboard shortcuts. For an overview of the available shortcuts, press `?` anywhere in the UI.
@@ -6,11 +6,11 @@ title: Telemetry FAQ
  <link rel="canonical" href="https://ranchermanager.docs.rancher.com/faq/telemetry"/>
 </head>
-### What is Telemetry?
+## What is Telemetry?
 Telemetry collects aggregate information about the size of Rancher installations, versions of components used, and which features are used.  This information is used by Rancher Labs to help make the product better and is not shared with third-parties.
-### What information is collected?
+## What information is collected?
 No specific identifying information like usernames, passwords, or the names or addresses of user resources will ever be collected.
@@ -24,12 +24,12 @@ The primary things collected include:
  - The image name & version of Rancher that is running.
  - A unique randomly-generated identifier for this installation.
-### Can I see the information that is being sent?
+## Can I see the information that is being sent?
 If Telemetry is enabled, you can go to `https://<your rancher server>/v1-telemetry` in your installation to see the current data.
 If Telemetry is not enabled, the process that collects the data is not running, so there is nothing being collected to look at.
-### How do I turn it on or off?
+## How do I turn it on or off?
 After initial setup, an administrator can go to the `Settings` page in the `Global` section of the UI and click Edit to change the `telemetry-opt` setting to either `in` or `out`.
@@ -12,7 +12,7 @@ These instructions assume you have already followed the instructions for a Kuber
 :::
-### Rancher Helm Upgrade Options
+## Rancher Helm Upgrade Options
 To upgrade with Helm, apply the same options that you used when installing Rancher. Refer to the reference table below to replace each placeholder. Rancher needs to be configured to use the private registry in order to provision any Rancher launched Kubernetes clusters or Rancher tools.
@@ -148,7 +148,7 @@ To see options on how to customize the cert-manager install (including for cases
 :::
 ```
-# If you have installed the CRDs manually instead of with the `--set installCRDs=true` option added to your Helm install command, you should upgrade your CRD resources before upgrading the Helm chart:
+# If you have installed the CRDs manually, instead of setting `installCRDs` or `crds.enabled` to `true` in your Helm install command, you should upgrade your CRD resources before upgrading the Helm chart:
 kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/<VERSION>/cert-manager.crds.yaml
 # Add the Jetstack Helm repository
@@ -161,7 +161,7 @@ helm repo update
 helm install cert-manager jetstack/cert-manager \
  --namespace cert-manager \
  --create-namespace \
-  --set installCRDs=true
+  --set crds.enabled=true
 ```
 Once you’ve installed cert-manager, you can verify it is deployed correctly by checking the cert-manager namespace for running pods:
@@ -49,7 +49,7 @@ See the [rancher/rancher-cleanup repo](https://github.com/rancher/rancher-cleanu
 ### Step 2: Restore the Backup and Bring Up Rancher
 At this point, there should be no Rancher-related resources on the upstream cluster. Therefore, the next step will be the same as if you were migrating Rancher to a new cluster that contains no Rancher resources.
-/home/btat/rancher-docs/docs/how-to-guides/new-user-guides/backup-restore-and-disaster-recovery/migrate-rancher-to-new-cluster.md
+
 Follow these [instructions](../../../how-to-guides/new-user-guides/backup-restore-and-disaster-recovery/migrate-rancher-to-new-cluster.md) to install the Rancher-Backup Helm chart and restore Rancher to its previous state.
 Please keep in mind that:
 1. Step 3 can be skipped, because the Cert-Manager app should still exist on the upstream (local) cluster if it was installed before.
@@ -49,7 +49,6 @@ For [air-gapped installs only,](../other-installation-methods/air-gapped-helm-cl
 Follow the steps to upgrade Rancher server:
 ### 1. Back up Your Kubernetes Cluster that is Running Rancher Server
 Use the [backup application](../../../how-to-guides/new-user-guides/backup-restore-and-disaster-recovery/back-up-rancher.md) to back up Rancher.
@@ -119,7 +118,6 @@ If you are installing Rancher in an air-gapped environment, skip the rest of thi
 :::
 Get the values, which were passed with `--set`, from the current Rancher Helm chart that is installed.
 ```
@@ -22,7 +22,7 @@ Starting with version 1.24, the above defaults to true.
 For users looking to use another container runtime, Rancher has the edge-focused K3s and datacenter-focused RKE2 Kubernetes distributions that use containerd as the default runtime. Imported RKE2 and K3s Kubernetes clusters can then be upgraded and managed through Rancher going forward.
-### FAQ
+## FAQ
 <br/>
@@ -46,6 +46,6 @@ A: You can use a runtime like containerd with Kubernetes that does not require D
 Q: If I am already using RKE1 and want to switch to RKE2, what are my migration options?
-A: Today, you can stand up a new cluster and migrate workloads to a new RKE2 cluster that uses containerd. Rancher is exploring the possibility of an in-place upgrade path.
+A: Today, you can stand up a new cluster and migrate workloads to a new RKE2 cluster that uses containerd. For details, see the [RKE to RKE2 Replatforming Guide](https://links.imagerelay.com/cdn/3404/ql/5606a3da2365422ab2250d348aa07112/rke_to_rke2_replatforming_guide.pdf).
 <br/>
@@ -28,7 +28,7 @@ For security purposes, SSL (Secure Sockets Layer) is required when using Rancher
 Choose from the following options:
-### Option A: Default Self-Signed Certificate
+## Option A: Default Self-Signed Certificate
 <details id="option-a">
  <summary>Click to expand</summary>
@@ -55,7 +55,7 @@ docker run -d --restart=unless-stopped \
 </details>
-### Option B: Bring Your Own Certificate: Self-Signed
+## Option B: Bring Your Own Certificate: Self-Signed
 <details id="option-b">
  <summary>Click to expand</summary>
@@ -98,7 +98,7 @@ docker run -d --restart=unless-stopped \
 </details>
-### Option C: Bring Your Own Certificate: Signed by Recognized CA
+## Option C: Bring Your Own Certificate: Signed by Recognized CA
 <details id="option-c">
  <summary>Click to expand</summary>
@@ -143,8 +143,6 @@ docker run -d --restart=unless-stopped \
 </details>
 :::note
 If you don't intend to send telemetry data, opt out [telemetry](../../../../faq/telemetry.md) during the initial login.
@@ -25,7 +25,7 @@ We recommend setting up the following infrastructure for a high-availability ins
 - **A DNS record** to map a URL to the load balancer. This will become the Rancher server URL, and downstream Kubernetes clusters will need to reach it.
 - **A private image registry** to distribute container images to your machines.
-### 1. Set up Linux Nodes
+## 1. Set up Linux Nodes
 These hosts will be disconnected from the internet, but require being able to connect with your private registry.
@@ -33,7 +33,7 @@ Make sure that your nodes fulfill the general installation requirements for [OS,
 For an example of one way to set up Linux nodes, refer to this [tutorial](../../../../how-to-guides/new-user-guides/infrastructure-setup/nodes-in-amazon-ec2.md) for setting up nodes as instances in Amazon EC2.
-### 2. Set up External Datastore
+## 2. Set up External Datastore
 The ability to run Kubernetes using a datastore other than etcd sets K3s apart from other Kubernetes distributions. This feature provides flexibility to Kubernetes operators. The available options allow you to select a datastore that best fits your use case.
@@ -49,7 +49,7 @@ For an example of one way to set up the database, refer to this [tutorial](../..
 For the complete list of options that are available for configuring a K3s cluster datastore, refer to the [K3s documentation.](https://rancher.com/docs/k3s/latest/en/installation/datastore/)
-### 3. Set up the Load Balancer
+## 3. Set up the Load Balancer
 You will also need to set up a load balancer to direct traffic to the Rancher replica on both nodes. That will prevent an outage of any single node from taking down communications to the Rancher management server.
@@ -72,7 +72,7 @@ Do not use this load balancer (i.e, the `local` cluster Ingress) to load balance
 :::
-### 4. Set up the DNS Record
+## 4. Set up the DNS Record
 Once you have set up your load balancer, you will need to create a DNS record to send traffic to this load balancer.
@@ -82,7 +82,7 @@ You will need to specify this hostname in a later step when you install Rancher,
 For a how-to guide for setting up a DNS record to route domain traffic to an Amazon ELB load balancer, refer to the [official AWS documentation.](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-to-elb-load-balancer)
-### 5. Set up a Private Image Registry
+## 5. Set up a Private Image Registry
 Rancher supports air gap installs using a private registry. You must have your own private registry or other means of distributing container images to your machines.
@@ -106,13 +106,13 @@ To install the Rancher management server on a high-availability RKE cluster, we
 These nodes must be in the same region/data center. You may place these servers in separate availability zones.
-### Why three nodes?
+## Why Three Nodes?
 In an RKE cluster, Rancher server data is stored on etcd. This etcd database runs on all three nodes.
 The etcd database requires an odd number of nodes so that it can always elect a leader with a majority of the etcd cluster. If the etcd database cannot elect a leader, etcd can suffer from [split brain](https://www.quora.com/What-is-split-brain-in-distributed-systems), requiring the cluster to be restored from backup. If one of the three etcd nodes fails, the two remaining nodes can elect a leader because they have the majority of the total number of etcd nodes.
-### 1. Set up Linux Nodes
+## 1. Set up Linux Nodes
 These hosts will be disconnected from the internet, but require being able to connect with your private registry.
@@ -120,7 +120,7 @@ Make sure that your nodes fulfill the general installation requirements for [OS,
 For an example of one way to set up Linux nodes, refer to this [tutorial](../../../../how-to-guides/new-user-guides/infrastructure-setup/nodes-in-amazon-ec2.md) for setting up nodes as instances in Amazon EC2.
-### 2. Set up the Load Balancer
+## 2. Set up the Load Balancer
 You will also need to set up a load balancer to direct traffic to the Rancher replica on both nodes. That will prevent an outage of any single node from taking down communications to the Rancher management server.
@@ -143,7 +143,7 @@ Do not use this load balancer (i.e, the `local` cluster Ingress) to load balance
 :::
-### 3. Set up the DNS Record
+## 3. Set up the DNS Record
 Once you have set up your load balancer, you will need to create a DNS record to send traffic to this load balancer.
@@ -153,7 +153,7 @@ You will need to specify this hostname in a later step when you install Rancher,
 For a how-to guide for setting up a DNS record to route domain traffic to an Amazon ELB load balancer, refer to the [official AWS documentation.](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-to-elb-load-balancer)
-### 4. Set up a Private Image Registry
+## 4. Set up a Private Image Registry
 Rancher supports air gap installs using a secure private registry. You must have your own private registry or other means of distributing container images to your machines.
@@ -176,7 +176,7 @@ If you need to create a private registry, refer to the documentation pages for y
 :::
-### 1. Set up a Linux Node
+## 1. Set up a Linux Node
 This host will be disconnected from the Internet, but needs to be able to connect to your private registry.
@@ -184,7 +184,7 @@ Make sure that your node fulfills the general installation requirements for [OS,
 For an example of one way to set up Linux nodes, refer to this [tutorial](../../../../how-to-guides/new-user-guides/infrastructure-setup/nodes-in-amazon-ec2.md) for setting up nodes as instances in Amazon EC2.
-### 2. Set up a Private Docker Registry
+## 2. Set up a Private Docker Registry
 Rancher supports air gap installs using a private registry on your bastion server. You must have your own private registry or other means of distributing container images to your machines.
@@ -193,4 +193,4 @@ If you need help with creating a private registry, please refer to the [official
 </TabItem>
 </Tabs>
-### [Next: Collect and Publish Images to your Private Registry](publish-images.md)
+## [Next: Collect and Publish Images to your Private Registry](publish-images.md)
@@ -23,14 +23,15 @@ The steps to set up an air-gapped Kubernetes cluster on RKE, RKE2, or K3s are sh
 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.
-### Installation Outline
+## Installation Outline
 1. [Prepare Images Directory](#1-prepare-images-directory)
 2. [Create Registry YAML](#2-create-registry-yaml)
 3. [Install K3s](#3-install-k3s)
 4. [Save and Start Using the kubeconfig File](#4-save-and-start-using-the-kubeconfig-file)
-### 1. Prepare Images Directory
+## 1. Prepare Images Directory
 Obtain the images tar file for your architecture from the [releases](https://github.com/k3s-io/k3s/releases) page for the version of K3s you will be running.
 Place the tar file in the `images` directory before starting K3s on each node, for example:
@@ -40,7 +41,8 @@ sudo mkdir -p /var/lib/rancher/k3s/agent/images/
 sudo cp ./k3s-airgap-images-$ARCH.tar /var/lib/rancher/k3s/agent/images/
 ```
-### 2. Create Registry YAML
+## 2. Create Registry YAML
 Create the registries.yaml file at `/etc/rancher/k3s/registries.yaml`. This will tell K3s the necessary details to connect to your private registry.
 The registries.yaml file should look like this before plugging in the necessary information:
@@ -66,7 +68,7 @@ Note, at this time only secure registries are supported with K3s (SSL with custo
 For more information on private registries configuration file for K3s, refer to the [K3s documentation.](https://rancher.com/docs/k3s/latest/en/installation/private-registry/)
-### 3. Install K3s
+## 3. Install K3s
 Rancher needs to be installed on a supported Kubernetes version. To find out which versions of Kubernetes are supported for your Rancher version, refer to the [Rancher Support Matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/).
@@ -98,7 +100,7 @@ K3s additionally provides a `--resolv-conf` flag for kubelets, which may help wi
 :::
-### 4. Save and Start Using the kubeconfig File
+## 4. Save and Start Using the kubeconfig File
 When you installed K3s on each Rancher server node, a `kubeconfig` file was created on the node at `/etc/rancher/k3s/k3s.yaml`. This file contains credentials for full access to the cluster, and you should save this file in a secure location.
@@ -138,7 +140,7 @@ kubectl --kubeconfig ~/.kube/config/k3s.yaml get pods --all-namespaces
 For more information about the `kubeconfig` file, refer to the [K3s documentation](https://rancher.com/docs/k3s/latest/en/cluster-access/) or the [official Kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/organize-cluster-access-kubeconfig/) about organizing cluster access using `kubeconfig` files.
-### Note on Upgrading
+## Note on Upgrading
 Upgrading an air-gap environment can be accomplished in the following manner:
@@ -151,14 +153,15 @@ Upgrading an air-gap environment can be accomplished in the following manner:
 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.
-### Installation Outline
+## Installation Outline
 1. [Create RKE2 configuration](#1-create-rke2-configuration)
 2. [Create Registry YAML](#2-create-registry-yaml)
 3. [Install RKE2](#3-install-rke2)
 4. [Save and Start Using the kubeconfig File](#4-save-and-start-using-the-kubeconfig-file)
-### 1. Create RKE2 configuration
+## 1. Create RKE2 configuration
 Create the config.yaml file at `/etc/rancher/rke2/config.yaml`. This will contain all the configuration options necessary to create a highly available RKE2 cluster.
 On the first server the minimum config is:
@@ -186,7 +189,8 @@ RKE2 additionally provides a `resolv-conf` option for kubelets, which may help w
 :::
-### 2. Create Registry YAML
+## 2. Create Registry YAML
 Create the registries.yaml file at `/etc/rancher/rke2/registries.yaml`. This will tell RKE2 the necessary details to connect to your private registry.
 The registries.yaml file should look like this before plugging in the necessary information:
@@ -210,7 +214,7 @@ configs:
 For more information on private registries configuration file for RKE2, refer to the [RKE2 documentation.](https://docs.rke2.io/install/containerd_registry_configuration)
-### 3. Install RKE2
+## 3. Install RKE2
 Rancher needs to be installed on a supported Kubernetes version. To find out which versions of Kubernetes are supported for your Rancher version, refer to the [support maintenance terms.](https://rancher.com/support-maintenance-terms/)
@@ -239,7 +243,7 @@ systemctl start rke2-server.service
 For more information, refer to the [RKE2 documentation](https://docs.rke2.io/install/airgap).
-### 4. Save and Start Using the kubeconfig File
+## 4. Save and Start Using the kubeconfig File
 When you installed RKE2 on each Rancher server node, a `kubeconfig` file was created on the node at `/etc/rancher/rke2/rke2.yaml`. This file contains credentials for full access to the cluster, and you should save this file in a secure location.
@@ -279,7 +283,7 @@ kubectl --kubeconfig ~/.kube/config/rke2.yaml get pods --all-namespaces
 For more information about the `kubeconfig` file, refer to the [RKE2 documentation](https://docs.rke2.io/cluster_access) or the [official Kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/organize-cluster-access-kubeconfig/) about organizing cluster access using `kubeconfig` files.
-### Note on Upgrading
+## Note on Upgrading
 Upgrading an air-gap environment can be accomplished in the following manner:
@@ -291,7 +295,7 @@ Upgrading an air-gap environment can be accomplished in the following manner:
 <TabItem value="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
+## 1. Install RKE
 Install RKE by following the instructions in the [RKE documentation.](https://rancher.com/docs/rke/latest/en/installation/)
@@ -301,7 +305,7 @@ Certified version(s) of RKE based on the Rancher version can be found in the [Ra
 :::
-### 2. Create an RKE Config File
+## 2. Create an RKE Config File
 From a system that can access ports 22/TCP and 6443/TCP on the Linux host node(s) that you set up in a previous step, use the sample below to create a new file named `rancher-cluster.yml`.
@@ -352,7 +356,7 @@ private_registries:
    is_default: true
 ```
-### 3. Run RKE
+## 3. Run RKE
 After configuring `rancher-cluster.yml`, bring up your Kubernetes cluster:
@@ -360,7 +364,7 @@ After configuring `rancher-cluster.yml`, bring up your Kubernetes cluster:
 rke up --config ./rancher-cluster.yml
 ```
-### 4. Save Your Files
+## 4. Save Your Files
 :::note Important:
@@ -383,8 +387,8 @@ The "rancher-cluster" parts of the two latter file names are dependent on how yo
 :::
-### Issues or errors?
+## Issues or Errors?
 See the [Troubleshooting](../../install-upgrade-on-a-kubernetes-cluster/troubleshooting.md) page.
-### [Next: Install Rancher](install-rancher-ha.md)
+## [Next: Install Rancher](install-rancher-ha.md)
@@ -8,7 +8,7 @@ title: 4. Install Rancher
 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
+## Privileged Access for Rancher
 When the Rancher server is deployed in the Docker container, a local Kubernetes cluster is installed within the container for Rancher to use. Because many features of Rancher run as deployments, and privileged mode is required to run containers within containers, you will need to install Rancher with the `--privileged` option.
@@ -92,7 +92,7 @@ Recent changes to cert-manager require an upgrade. If you are upgrading Rancher
 :::
-##### 1. Add the cert-manager repo
+##### 1. Add the cert-manager Repo
 From a system connected to the internet, add the cert-manager repo to Helm:
@@ -101,7 +101,7 @@ helm repo add jetstack https://charts.jetstack.io
 helm repo update
 ```
-##### 2. Fetch the cert-manager chart
+##### 2. Fetch the cert-manager Chart
 Fetch the latest cert-manager chart available from the [Helm chart repository](https://artifacthub.io/packages/helm/cert-manager/cert-manager).
@@ -109,7 +109,7 @@ Fetch the latest cert-manager chart available from the [Helm chart repository](h
 helm fetch jetstack/cert-manager --version v1.11.0
 ```
-##### 3. Retrieve the Cert-Manager CRDs
+##### 3. Retrieve the cert-manager CRDs
 Download the required CRD file for cert-manager:
   ```plain
@@ -120,7 +120,7 @@ Download the required CRD file for cert-manager:
 Copy the fetched charts to a system that has access to the Rancher server cluster to complete installation.
-##### 1. Install Cert-Manager
+#### 1. Install cert-manager
 Install cert-manager with the same options you would use to install the chart. Remember to set the `image.repository` option to pull the image from your private registry.
@@ -160,7 +160,8 @@ If you are using self-signed certificates, install cert-manager:
 </details>
-##### 2. Install Rancher
+#### 2. Install Rancher
 First, refer to [Adding TLS Secrets](../../resources/add-tls-secrets.md) to publish the certificate files so Rancher and the ingress controller can use them.
 Then, create the namespace for Rancher using kubectl:
@@ -192,9 +193,9 @@ Placeholder | Description
 **Optional**: To install a specific Rancher version, set the `rancherImageTag` value, example: `--set rancherImageTag=v2.5.8`
-#### Option B: Certificates From Files using Kubernetes Secrets
+#### Option B: Certificates From Files Using Kubernetes Secrets
-##### 1. Create secrets
+##### 1. Create Secrets
 Create Kubernetes secrets from your own certificates for Rancher to use. The common name for the cert will need to match the `hostname` option in the command below, or the ingress controller will fail to provision the site for Rancher.
@@ -27,7 +27,7 @@ First configure the HTTP proxy settings on the K3s systemd service, so that K3s'
 ```
 cat <<'EOF' | sudo tee /etc/default/k3s > /dev/null
 HTTP_PROXY=http://${proxy_host}
-HTTPS_PROXY=http://${proxy_host}"
+HTTPS_PROXY=http://${proxy_host}
 NO_PROXY=127.0.0.0/8,10.0.0.0/8,cattle-system.svc,172.16.0.0/12,192.168.0.0/16,.svc,.cluster.local
 EOF
 ```
@@ -71,7 +71,7 @@ Then you have to configure the HTTP proxy settings on the RKE2 systemd service,
 ```
 cat <<'EOF' | sudo tee /etc/default/rke2-server > /dev/null
 HTTP_PROXY=http://${proxy_host}
-HTTPS_PROXY=http://${proxy_host}"
+HTTPS_PROXY=http://${proxy_host}
 NO_PROXY=127.0.0.0/8,10.0.0.0/8,cattle-system.svc,172.16.0.0/12,192.168.0.0/16,.svc,.cluster.local
 EOF
 ```
@@ -36,7 +36,7 @@ Administrators might configure the RKE metadata settings to do the following:
 - Change the metadata URL that Rancher uses to sync the metadata, which is useful for air gap setups if you need to sync Rancher locally instead of with GitHub
 - Prevent Rancher from auto-syncing the metadata, which is one way to prevent new and unsupported Kubernetes versions from being available in Rancher
-### Refresh Kubernetes Metadata
+## Refresh Kubernetes Metadata
 The option to refresh the Kubernetes metadata is available for administrators by default, or for any user who has the **Manage Cluster Drivers** [global role.](../../how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/manage-role-based-access-control-rbac/global-permissions.md)
@@ -74,7 +74,7 @@ If you don't have an air gap setup, you don't need to specify the URL where Ranc
 However, if you have an [air gap setup,](#air-gap-setups) you will need to mirror the Kubernetes metadata repository in a location available to Rancher. Then you need to change the URL to point to the new location of the JSON file.
-### Air Gap Setups
+## Air Gap Setups
 Rancher relies on a periodic refresh of the `rke-metadata-config` to download new Kubernetes version metadata if it is supported with the current version of the Rancher server. For a table of compatible Kubernetes and Rancher versions, refer to the [service terms section.](https://rancher.com/support-maintenance-terms/all-supported-versions/rancher-v2.2.8/)
@@ -10,7 +10,7 @@ When Rancher is used to manage [a large infrastructure](../../getting-started/in
 The etcd data set is automatically cleaned up on a five minute interval by Kubernetes. There are situations, e.g. deployment thrashing, where enough events could be written to etcd and deleted before garbage collection occurs and cleans things up causing the keyspace to fill up. If you see `mvcc: database space exceeded` errors, in the etcd logs or Kubernetes API server logs, you should consider increasing the keyspace size. This can be accomplished by setting the [quota-backend-bytes](https://etcd.io/docs/v3.5/op-guide/maintenance/#space-quota) setting on the etcd servers.
-### Example: This snippet of the RKE cluster.yml file increases the keyspace size to 5GB
+## Example: This Snippet of the RKE Cluster.yml file Increases the Keyspace Size to 5GB
 ```yaml
 # RKE cluster.yml
@@ -21,7 +21,7 @@ services:
      quota-backend-bytes: 5368709120
 ```
-## Scaling etcd disk performance
+## Scaling etcd Disk Performance
 You can follow the recommendations from [the etcd docs](https://etcd.io/docs/v3.5/tuning/#disk) on how to tune the disk priority on the host.
@@ -54,8 +54,20 @@ Since the private registry cannot be configured after the cluster is created, yo
 1. Select **☰ > Cluster Management**.
 1. On the **Clusters** page, click **Create**.
 1. Choose a cluster type.
-1. In the **Cluster Configuration** go to the **Registries** tab and select **Pull images for Rancher from a private registry**.
+1. In the **Cluster Configuration** go to the **Registries** tab.
-1. Enter the registry hostname and credentials.
+1. Check the box next to **Enable cluster scoped container registry for Rancher system container images**.
 1. Enter the registry hostname.
 1. Under **Authentication** select **Create a HTTP Basic Auth Secret** and fill in the credential fields.
 1. Click **Create**.
 **Result:** The new cluster pulls images from the private registry.
 ### Working with Private Registry Credentials
 When working with private registries, it is important to ensure that any secrets created for these registries are properly backed up. When you add a private registry credential secret through the Rancher GUI and select **Create a HTTP Basic Auth Secret**, the secret is included in backup operations using Rancher Backups.
 However, if you create a credential secret outside of the Rancher GUI, such as by using kubectl or Terraform, you must add the `fleet.cattle.io/managed=true` label to indicate that the secret should be included in backups created by Rancher Backups.
 For example, if you have a custom private registry named "my-private-registry" and create a secret called "my-reg-creds" for it, apply the `fleet.cattle.io/managed=true` label to this secret. This ensures that your backup process captures the secret, providing easy restoration if needed.
 By following this guidance, you can ensure that all of your private registry credentials are backed up and easily accessible in the event of a restore or migration.
@@ -19,7 +19,7 @@ These nodes must be in the same region. You may place these servers in separate
 To install the Rancher management server on a high-availability RKE2 cluster, we recommend setting up the following infrastructure:
 - **Three Linux nodes,** typically virtual machines, in the infrastructure provider of your choice.
- **A load balancer** to direct traffic to the two nodes.
+- **A load balancer** to direct traffic to the nodes.
 - **A DNS record** to map a URL to the load balancer. This will become the Rancher server URL, and downstream Kubernetes clusters will need to reach it.
 ### 1. Set up Linux Nodes
@@ -51,7 +51,7 @@ Do not use this load balancer (i.e, the `local` cluster Ingress) to load balance
 :::
-### 4. Set up the DNS Record
+### 3. Set up the DNS Record
 Once you have set up your load balancer, you will need to create a DNS record to send traffic to this load balancer.
@@ -59,4 +59,4 @@ Depending on your environment, this may be an A record pointing to the load bala
 You will need to specify this hostname in a later step when you install Rancher, and it is not possible to change it later. Make sure that your decision is a final one.
-For a how-to guide for setting up a DNS record to route domain traffic to an Amazon ELB load balancer, refer to the [official AWS documentation.](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-to-elb-load-balancer)
+For a how-to guide for setting up a DNS record to route domain traffic to an Amazon ELB load balancer, refer to the [official AWS documentation.](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-to-elb-load-balancer)
@@ -134,6 +134,7 @@ Resource targeting uses `*` as the ARN of many of the resources created cannot b
                "ec2:DescribeAvailabilityZones",
                "ec2:DescribeAccountAttributes",
                "ec2:DeleteTags",
                "ec2:DeleteLaunchTemplateVersions",
                "ec2:DeleteLaunchTemplate",
                "ec2:DeleteSecurityGroup",
                "ec2:DeleteKeyPair",
@@ -321,7 +322,7 @@ These are permissions that are needed by Rancher to create a Virtual Private Clo
 ### EBS CSI Driver addon Permissions
-Permissions required for Rancher to install the Amazon EBS CSI Driver add-on.
+The following are the required permissions for installing the Amazon EBS CSI Driver add-on.
 ```json
 {
@@ -29,7 +29,7 @@ If you create a namespace with `kubectl`, it may be unusable because `kubectl` d
 :::
-### Creating Namespaces
+## Creating Namespaces
 Create a new namespace to isolate apps and resources in a project.
@@ -50,7 +50,7 @@ When working with project resources that you can assign to a namespace (i.e., [w
 **Result:** Your namespace is added to the project. You can begin assigning cluster resources to the namespace.
-### Moving Namespaces to Another Project
+## Moving Namespaces to Another Project
 Cluster admins and members may occasionally need to move a namespace to another project, such as when you want a different team to start using the application.
@@ -71,7 +71,7 @@ Cluster admins and members may occasionally need to move a namespace to another
 **Result:** Your namespace is moved to a different project (or is unattached from all projects). If any project resources are attached to the namespace, the namespace releases them and then attached resources from the new project.
-### Editing Namespace Resource Quotas
+## Editing Namespace Resource Quotas
 You can always override the namespace default limit to provide a specific namespace with access to more (or less) project resources.
@@ -14,7 +14,7 @@ To configure the custom resources, go to the **Cluster Dashboard** To configure
 1. On the **Clusters** page, go to the cluster where you want to configure CIS scans and click **Explore**.
 1. In the left navigation bar, click **CIS Benchmark**.
-### Scans
+## Scans
 A scan is created to trigger a CIS scan on the cluster based on the defined profile. A report is created after the scan is completed.
@@ -31,7 +31,7 @@ spec:
  scanProfileName: rke-profile-hardened
 ```
-### Profiles
+## Profiles
 A profile contains the configuration for the CIS scan, which includes the benchmark version to use and any specific tests to skip in that benchmark.
@@ -66,7 +66,7 @@ spec:
    - "1.1.21"
 ```
-### Benchmark Versions
+## Benchmark Versions
 A benchmark version is the name of benchmark to run using `kube-bench`, as well as the valid configuration parameters for that benchmark.
@@ -17,7 +17,7 @@ When a cluster scan is run, you need to select a Profile which points to a speci
 Follow all the steps below to add a custom Benchmark Version and run a scan using it.
-### 1. Prepare the Custom Benchmark Version ConfigMap
+## 1. Prepare the Custom Benchmark Version ConfigMap
 To create a custom benchmark version, first you need to create a ConfigMap containing the benchmark version's config files and upload it to your Kubernetes cluster where you want to run the scan.
@@ -42,7 +42,7 @@ To prepare a custom benchmark version ConfigMap, suppose we want to add a custom
    kubectl create configmap -n <namespace> foo --from-file=<path to directory foo>
    ```
-### 2. Add a Custom Benchmark Version to a Cluster
+## 2. Add a Custom Benchmark Version to a Cluster
 1. In the upper left corner, click **☰ > Cluster Management**.
 1. On the **Clusters** page, go to the cluster where you want to add a custom benchmark and click **Explore**.
@@ -54,7 +54,7 @@ To prepare a custom benchmark version ConfigMap, suppose we want to add a custom
 1. Add the minimum and maximum Kubernetes version limits applicable, if any.
 1. Click **Create**.
-### 3. Create a New Profile for the Custom Benchmark Version
+## 3. Create a New Profile for the Custom Benchmark Version
 To run a scan using your custom benchmark version, you need to add a new Profile pointing to this benchmark version.
@@ -66,7 +66,7 @@ To run a scan using your custom benchmark version, you need to add a new Profile
 1. Choose the Benchmark Version from the dropdown.
 1. Click **Create**.
-### 4. Run a Scan Using the Custom Benchmark Version
+## 4. Run a Scan Using the Custom Benchmark Version
 Once the Profile pointing to your custom benchmark version `foo` has been created, you can create a new Scan to run the custom test configs in the Benchmark Version.
@@ -18,8 +18,10 @@ In order to deploy and run the adapter successfully, you need to ensure its vers
 :::
 | Rancher Version | Adapter Version  |
-|-----------------|:----------------:|
+|-----------------|------------------|
-| v2.9.0          | v104.0.0+up4.0.0  |
+| v2.9.2          | v104.0.0+up4.0.0 |
 | v2.9.1          | v104.0.0+up4.0.0 |
 | v2.9.0          | v104.0.0+up4.0.0 |
 ### 1. Gain Access to the Local Cluster
@@ -1,5 +1,5 @@
 ---
-title: Supportconfig bundle
+title: Supportconfig Bundle
 ---
 <head>
@@ -12,7 +12,7 @@ These bundles can be created through Rancher or through direct access to the clu
 > **Note:** Only admin users can generate/download supportconfig bundles, regardless of method.
-### Accessing through Rancher
+## Accessing Through Rancher
 First, click on the hamburger menu. Then click the `Get Support` button.
@@ -24,7 +24,7 @@ In the next page, click on the `Generate Support Config` button.
 ![Get Support](/img/generate-support-config.png)
-### Accessing without rancher
+## Accessing Without Rancher
 First, generate a kubeconfig for the cluster that Rancher is installed on.
@@ -6,7 +6,7 @@ title: Cluster API (CAPI) with Rancher Turtles
  <link rel="canonical" href="https://ranchermanager.docs.rancher.com/integrations-in-rancher/cluster-api"/>
 </head>
-[Rancher Turtles](https://turtles.docs.rancher.com/) is a [Rancher extension](../rancher-extensions.md) that manages the lifecycle of provisioned Kubernetes clusters, by providing integration between your Cluster API (CAPI) and Rancher. With Rancher Turtles, you can:
+[Rancher Turtles](https://turtles.docs.rancher.com/) is a [Kubernetes Operator](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/#operators-in-kubernetes) that manages the lifecycle of provisioned Kubernetes clusters, by providing integration between your Cluster API (CAPI) and Rancher. With Rancher Turtles, you can:
 - Import CAPI clusters into Rancher, by installing the Rancher Cluster Agent in CAPI provisioned clusters.
 - Configure the [CAPI Operator](https://turtles.docs.rancher.com/reference-guides/rancher-turtles-chart/values#cluster-api-operator-values).
@@ -8,7 +8,7 @@ title: Overview
 Introduced in Rancher v2.6.1, [Harvester](https://docs.harvesterhci.io/) is an open-source hyper-converged infrastructure (HCI) software built on Kubernetes. Harvester installs on bare metal servers and provides integrated virtualization and distributed storage capabilities. Although Harvester operates using Kubernetes, it does not require users to know Kubernetes concepts, making it a more user-friendly application.
-### Feature Flag
+## Feature Flag
 The Harvester feature flag is used to manage access to the Virtualization Management (VM) page in Rancher where users can navigate directly to Harvester clusters and access the Harvester UI. The Harvester feature flag is enabled by default. Click [here](../../how-to-guides/advanced-user-guides/enable-experimental-features/enable-experimental-features.md) for more information on feature flags in Rancher.
@@ -22,7 +22,7 @@ To navigate to the Harvester cluster, click **☰ > Virtualization Management**.
 * Users may import a Harvester cluster only on the Virtualization Management page. Importing a cluster on the Cluster Management page is not supported, and a warning will advise you to return to the VM page to do so.
-### Harvester Node Driver
+## Harvester Node Driver
 The [Harvester node driver](https://docs.harvesterhci.io/v1.1/rancher/node/node-driver/) is generally available for RKE and RKE2 options in Rancher. The node driver is available whether or not the Harvester feature flag is enabled. Note that the node driver is off by default. Users may create RKE or RKE2 clusters on Harvester only from the Cluster Management page.
@@ -30,7 +30,7 @@ Harvester allows `.ISO` images to be uploaded and displayed through the Harveste
 See [Provisioning Drivers](../../how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md#node-drivers) for more information on node drivers in Rancher.
-### Port Requirements
+## Port Requirements
 The port requirements for the Harvester cluster can be found [here](https://docs.harvesterhci.io/v1.1/install/requirements#networking).
@@ -15,4 +15,4 @@ To learn more and get started with Rancher Prime, please visit [this page](https
 import DocCardList from '@theme/DocCardList';
 import { useCurrentSidebarCategory } from '@docusaurus/theme-common/internal';
-<DocCardList items={useCurrentSidebarCategory().items.slice(0,8)} />
+<DocCardList items={useCurrentSidebarCategory().items.slice(0,9)} />
@@ -10,7 +10,7 @@ This section summarizes the architecture of the Rancher logging application.
 For more details about how the Logging operator works, see the [official documentation.](https://kube-logging.github.io/docs/#architecture)
-### How the Logging Operator Works
+## How the Logging Operator Works
 The Logging operator automates the deployment and configuration of a Kubernetes logging pipeline. It deploys and configures a Fluent Bit DaemonSet on every node to collect container and application logs from the node file system.
@@ -6,7 +6,7 @@ title: rancher-logging Helm Chart Options
  <link rel="canonical" href="https://ranchermanager.docs.rancher.com/integrations-in-rancher/logging/logging-helm-chart-options"/>
 </head>
-### Enable/Disable Windows Node Logging
+## Enable/Disable Windows Node Logging
 You can enable or disable Windows node logging by setting `global.cattle.windows.enabled` to either `true` or `false` in the `values.yaml`.
@@ -21,7 +21,7 @@ Currently an [issue](https://github.com/rancher/rancher/issues/32325) exists whe
 :::
-### Working with a Custom Docker Root Directory
+## Working with a Custom Docker Root Directory
 If using a custom Docker root directory, you can set `global.dockerRootDirectory` in `values.yaml`.
@@ -31,11 +31,11 @@ Note that this only affects Linux nodes.
 If there are any Windows nodes in the cluster, the change will not be applicable to those nodes.
-### Adding NodeSelector Settings and Tolerations for Custom Taints
+## Adding NodeSelector Settings and Tolerations for Custom Taints
 You can add your own `nodeSelector` settings and add `tolerations` for additional taints by editing the logging Helm chart values. For details, see [this page.](taints-and-tolerations.md)
-### Enabling the Logging Application to Work with SELinux
+## Enabling the Logging Application to Work with SELinux
 :::note Requirements:
@@ -49,7 +49,7 @@ To use Logging v2 with SELinux, we recommend installing the `rancher-selinux` RP
 Then, when installing the logging application, configure the chart to be SELinux aware by changing `global.seLinux.enabled` to `true` in the `values.yaml`.
-### Additional Logging Sources
+## Additional Logging Sources
 By default, Rancher collects logs for [control plane components](https://kubernetes.io/docs/concepts/overview/components/#control-plane-components) and [node components](https://kubernetes.io/docs/concepts/overview/components/#node-components) for all cluster types.
@@ -72,7 +72,7 @@ When enabled, Rancher collects all additional node and control plane logs the pr
 If you're already using a cloud provider's own logging solution such as AWS CloudWatch or Google Cloud operations suite (formerly Stackdriver), it is not necessary to enable this option as the native solution will have unrestricted access to all logs.
-### Systemd Configuration
+## Systemd Configuration
 In Rancher logging, `SystemdLogPath` must be configured for K3s and RKE2 Kubernetes distributions.
@@ -87,7 +87,7 @@ K3s and RKE2 Kubernetes distributions log to journald, which is the subsystem of
  * If `/var/log/journal` exists, then use `/var/log/journal`.
  * If `/var/log/journal` does not exist, then use `/run/log/journal`.
-:::note Notes:
+:::note
 If any value not described above is returned, Rancher Logging will not be able to collect control plane logs. To address this issue, you will need to perform the following actions on every control plane node:
@@ -20,7 +20,7 @@ Both provide choice for the what node(s) the pod will run on.
 - [Adding NodeSelector Settings and Tolerations for Custom Taints](#adding-nodeselector-settings-and-tolerations-for-custom-taints)
-### Default Implementation in Rancher's Logging Stack
+## Default Implementation in Rancher's Logging Stack
 By default, Rancher taints all Linux nodes with `cattle.io/os=linux`, and does not taint Windows nodes.
 The logging stack pods have `tolerations` for this taint, which enables them to run on Linux nodes.
@@ -47,7 +47,7 @@ In the above example, we ensure that our pod only runs on Linux nodes, and we ad
 You can do the same with Rancher's existing taints, or with your own custom ones.
-### Adding NodeSelector Settings and Tolerations for Custom Taints
+## Adding NodeSelector Settings and Tolerations for Custom Taints
 If you would like to add your own `nodeSelector` settings, or if you would like to add `tolerations` for additional taints, you can pass the following to the chart's values.
@@ -25,7 +25,7 @@ With Longhorn, you can:
 ![Longhorn Dashboard](/img/longhorn-screenshot.png)
-### Installing Longhorn with Rancher
+## Installing Longhorn with Rancher
 1. Fulfill all [Installation Requirements.](https://longhorn.io/docs/latest/deploy/install/#installation-requirements)
 1. Go to the cluster where you want to install Longhorn.
@@ -37,14 +37,14 @@ With Longhorn, you can:
 **Result:** Longhorn is deployed in the Kubernetes cluster.
-### Accessing Longhorn from the Rancher UI
+## Accessing Longhorn from the Rancher UI
 1. Go to the cluster where Longhorn is installed. In the left navigation menu, click **Longhorn**.
 1. On this page, you can edit Kubernetes resources managed by Longhorn. To view the Longhorn UI, click the **Longhorn** button in the **Overview** section.
 **Result:** You will be taken to the Longhorn UI, where you can manage your Longhorn volumes and their replicas in the Kubernetes cluster, as well as secondary backups of your Longhorn storage that may exist in another Kubernetes cluster or in S3.
-### Uninstalling Longhorn from the Rancher UI
+## Uninstalling Longhorn from the Rancher UI
 1. Go to the cluster where Longhorn is installed and click **Apps**.
 1. Click **Installed Apps**.
@@ -53,15 +53,15 @@ With Longhorn, you can:
 **Result:** Longhorn is uninstalled.
-### GitHub Repository
+## GitHub Repository
 The Longhorn project is available [here.](https://github.com/longhorn/longhorn)
-### Documentation
+## Documentation
 The Longhorn documentation is [here.](https://longhorn.io/docs/)
-### Architecture
+## Architecture
 Longhorn creates a dedicated storage controller for each volume and synchronously replicates the volume across multiple replicas stored on multiple nodes.
@@ -15,7 +15,7 @@ For information on V1 monitoring and alerting, available in Rancher v2.2 up to v
 Using the `rancher-monitoring` application, you can quickly deploy leading open-source monitoring and alerting solutions onto your cluster.
-### Features
+## Features
 Prometheus lets you view metrics from your Rancher and Kubernetes objects. Using timestamps, Prometheus lets you query and view these metrics in easy-to-read graphs and visuals, either through the Rancher UI or Grafana, which is an analytics viewing platform deployed along with Prometheus.
@@ -97,7 +97,6 @@ To be able to fully deploy Monitoring V2 for Windows, all of your Windows hosts
 For more details on how to upgrade wins on existing Windows hosts, see [Windows cluster support for Monitoring V2.](windows-support.md).
 ## Known Issues
 There is a [known issue](https://github.com/rancher/rancher/issues/28787#issuecomment-693611821) that K3s clusters require more than the allotted default memory. If you enable monitoring on a K3s cluster, set `prometheus.prometheusSpec.resources.memory.limit` to 2500 Mi and `prometheus.prometheusSpec.resources.memory.request` to 1750 Mi.
@@ -6,13 +6,11 @@ title: Overview
  <link rel="canonical" href="https://ranchermanager.docs.rancher.com/integrations-in-rancher/neuvector/overview"/>
 </head>
 ### NeuVector Integration in Rancher
 [NeuVector 5.x](https://open-docs.neuvector.com/) is an open-source container-centric security platform that is integrated with Rancher. NeuVector offers real-time compliance, visibility, and protection for critical applications and data during runtime. NeuVector provides a firewall, container process/file system monitoring, security auditing with CIS benchmarks, and vulnerability scanning. For more information on Rancher security, please see the [security documentation](../../reference-guides/rancher-security/rancher-security.md).
 NeuVector can be enabled through a Helm chart that may be installed either through **Apps** or through the **Cluster Tools** button in the Rancher UI. Once the Helm chart is installed, users can easily [deploy and manage NeuVector clusters within Rancher](https://open-docs.neuvector.com/deploying/rancher#deploy-and-manage-neuvector-through-rancher-apps-marketplace).
-### Installing NeuVector with Rancher
+## Installing NeuVector with Rancher
 The Harvester Helm Chart is used to manage access to the NeuVector UI in Rancher where users can navigate directly to deploy and manage their NeuVector clusters.
@@ -44,12 +42,12 @@ Some examples are as follows:
 1. Click on **Cluster Tools** at the bottom of the left navigation bar.
 1. Repeat step 4 above to select your container runtime accordingly, then click **Install** again.
-### Accessing NeuVector from the Rancher UI
+## Accessing NeuVector from the Rancher UI
 1. Navigate to the cluster explorer of the cluster where NeuVector is installed. In the left navigation bar, click **NeuVector**.
 1. Click the external link to go to the NeuVector UI. Once the link is selected, users must accept the `END USER LICENSE AGREEMENT` to access the NeuVector UI.
-### Uninstalling NeuVector from the Rancher UI
+## Uninstalling NeuVector from the Rancher UI
 **To uninstall from Apps:**
@@ -62,15 +60,15 @@ Some examples are as follows:
 1. Click **☰ > Cluster Management**.
 1. Click on **Cluster Tools** at the bottom-left of the screen, then click on the trash can icon under the NeuVector chart. Select `Delete the CRD associated with this app` if desired, then click **Delete**.
-### GitHub Repository
+## GitHub Repository
 The NeuVector project is available [here](https://github.com/neuvector/neuvector).
-### Documentation
+## Documentation
 The NeuVector documentation is [here](https://open-docs.neuvector.com/).
-### Architecture
+## Architecture
 The NeuVector security solution contains four types of security containers: Controllers, Enforcers, Managers, and Scanners. A special container called an All-in-One is also provided to combine the Controller, Enforcer, and Manager functions all in one container, primarily for Docker-native deployments. There is also an Updater which, when run, will update the CVE database.
@@ -91,7 +89,7 @@ The NeuVector security solution contains four types of security containers: Cont
 To learn more about NeuVector's architecture, please refer [here](https://open-docs.neuvector.com/basics/overview#architecture).
-### CPU and Memory Allocations
+## CPU and Memory Allocations
 Below are the minimum recommended computing resources for the NeuVector chart installation in a default deployment. Note that the resource limit is not set.
@@ -105,7 +103,7 @@ Below are the minimum recommended computing resources for the NeuVector chart in
 \* Minimum 1GB of memory total required for Controller, Manager, and Scanner containers combined.
-### Hardened Cluster Support - Calico and Canal
+## Hardened Cluster Support - Calico and Canal
 <Tabs>
 <TabItem value="RKE1">
@@ -162,7 +160,7 @@ Below are the minimum recommended computing resources for the NeuVector chart in
 </Tabs>
-### SELinux-enabled Cluster Support - Calico and Canal
+## SELinux-enabled Cluster Support - Calico and Canal
 To enable SELinux on RKE2 clusters, follow the steps below:
@@ -179,12 +177,11 @@ kubectl patch deploy neuvector-scanner-pod -n cattle-neuvector-system --patch '{
 kubectl patch cronjob neuvector-updater-pod -n cattle-neuvector-system --patch '{"spec":{"jobTemplate":{"spec":{"template":{"spec":{"securityContext":{"runAsUser": 5400}}}}}}}'
 ```
-### Cluster Support in an Air-Gapped Environment
+## Cluster Support in an Air-Gapped Environment
 - All NeuVector components are deployable on a cluster in an air-gapped environment without any additional configuration needed.
-
+## Support Limitations
 ### Support Limitations
 * Only admins and cluster owners are currently supported.
@@ -192,12 +189,10 @@ kubectl patch cronjob neuvector-updater-pod -n cattle-neuvector-system --patch '
 * NeuVector is not supported on a Windows cluster.
-
+## Other Limitations
 ### Other Limitations
 * Currently, NeuVector feature chart installation fails when a NeuVector partner chart already exists. To work around this issue, uninstall the NeuVector partner chart and reinstall the NeuVector feature chart.
 * Sometimes when the controllers are not ready, the NeuVector UI is not accessible from the Rancher UI. During this time, controllers will try to restart, and it takes a few minutes for the controllers to be active.
 * Container runtime is not auto-detected for different cluster types when installing the NeuVector chart. To work around this, you can specify the runtime manually.
@@ -0,0 +1,21 @@
 ---
 title: SUSE Observability
 ---
 <head>
  <link rel="canonical" href="https://ranchermanager.docs.rancher.com/integrations-in-rancher/suse-observability"/>
 </head>
 SUSE Observability is a complete observability solution that provides deep insights into the health of your clusters and nodes, and the workloads running on them. Designed to give you clear visibility into your entire Kubernetes environment, SUSE Observability’s full-stack approach allows you to seamlessly explore everything from services to infrastructure within a single platform, eliminating the need for multiple observability tools.
 SUSE Observability securely collects and correlates data, offering actionable insights into both existing and potential issues in your cluster. This helps you address current problems swiftly and take preventative measures against future challenges.
 The intuitive dashboards highlight problem areas and offer remediation steps, guiding you from issue identification to root cause analysis, and ultimately to resolution, in the quickest possible time.
 For more information and to set up SUSE Observability in your SUSE Rancher-managed Kubernetes cluster, please refer to the [documentation](https://docs.stackstate.com/).
 :::note 
 The documentation portal for SUSE Observability is currently under development. In the coming months, the portal will be rolled out featuring comprehensive guides, tutorials, and references to support you on your SUSE Observability journey. Stay tuned!
 :::
@@ -9,7 +9,7 @@ description: Interact with Rancher using command line interface (CLI) tools from
 The Rancher CLI (Command Line Interface) is a unified tool that you can use to interact with Rancher. With this tool, you can operate Rancher using a command line rather than the GUI.
-### Download Rancher CLI
+## Download Rancher CLI
 The binary can be downloaded directly from the UI.
@@ -17,14 +17,14 @@ The binary can be downloaded directly from the UI.
 1. At the bottom of the navigation sidebar menu, click **About**.
 1. Under the **CLI Downloads section**, there are links to download the binaries for Windows, Mac, and Linux. You can also check the [releases page for our CLI](https://github.com/rancher/cli/releases) for direct downloads of the binary.
-### Requirements
+## Requirements
 After you download the Rancher CLI, you need to make a few configurations. Rancher CLI requires:
 - Your Rancher Server URL, which is used to connect to Rancher Server.
 - An API Bearer Token, which is used to authenticate with Rancher. For more information about obtaining a Bearer Token, see [Creating an API Key](../user-settings/api-keys.md).
-### CLI Authentication
+## CLI Authentication
 Before you can use Rancher CLI to control your Rancher Server, you must authenticate using an API Bearer Token. Log in using the following command (replace `<BEARER_TOKEN>` and `<SERVER_URL>` with your information):
@@ -34,7 +34,7 @@ $ ./rancher login https://<SERVER_URL> --token <BEARER_TOKEN>
 If Rancher Server uses a self-signed certificate, Rancher CLI prompts you to continue with the connection.
-### Project Selection
+## Project Selection
 Before you can perform any commands, you must select a Rancher project to perform those commands against. To select a [project](../../how-to-guides/new-user-guides/manage-clusters/projects-and-namespaces.md) to work on, use the command `./rancher context switch`. When you enter this command, a list of available projects displays. Enter a number to choose your project.
@@ -58,7 +58,7 @@ INFO[0005] Saving config to /Users/markbishop/.ranchcli2.json
 Ensure you can run `rancher kubectl get pods` successfully.
-### Commands
+## Commands
 The following commands are available for use in Rancher CLI.
@@ -86,12 +86,12 @@ The following commands are available for use in Rancher CLI.
 | `token`  | Authenticates and generates new kubeconfig token.  |
 | `help, [h]`  | Shows a list of commands or help for one command.  |
-### Rancher CLI Help
+## Rancher CLI Help
 Once logged into Rancher Server using the CLI, enter `./rancher --help` for a list of commands.
 All commands accept the `--help` flag, which documents each command's usage.
-### Limitations
+## Limitations
 The Rancher CLI **cannot** be used to install [dashboard apps or Rancher feature charts](../../how-to-guides/new-user-guides/helm-charts-in-rancher/helm-charts-in-rancher.md).
@@ -10,7 +10,7 @@ After you provision a Kubernetes cluster using Rancher, you can still edit optio
 For information on editing cluster membership, go to [this page.](../../how-to-guides/new-user-guides/manage-clusters/access-clusters/add-users-to-clusters.md)
-### Cluster Configuration References
+## Cluster Configuration References
 The cluster configuration options depend on the type of Kubernetes cluster:
@@ -21,7 +21,7 @@ The cluster configuration options depend on the type of Kubernetes cluster:
 - [GKE Cluster Configuration](rancher-server-configuration/gke-cluster-configuration/gke-cluster-configuration.md)
 - [AKS Cluster Configuration](rancher-server-configuration/aks-cluster-configuration.md)
-### Cluster Management Capabilities by Cluster Type
+## Cluster Management Capabilities by Cluster Type
 The options and settings available for an existing cluster change based on the method that you used to provision it.
@@ -6,15 +6,15 @@ title: Monitoring Configuration Examples
  <link rel="canonical" href="https://ranchermanager.docs.rancher.com/reference-guides/monitoring-v2-configuration/examples"/>
 </head>
-### ServiceMonitor
+## ServiceMonitor
 See the official prometheus-operator GitHub repo for an example [ServiceMonitor](https://github.com/prometheus-operator/prometheus-operator/blob/master/example/prometheus-operator-crd/monitoring.coreos.com_servicemonitors.yaml) YAML.
-### PodMonitor
+## PodMonitor
 See the [Prometheus Operator documentation](https://prometheus-operator.dev/docs/user-guides/getting-started/#using-podmonitors) for an example PodMonitor and an example Prometheus resource that refers to a PodMonitor.
-### PrometheusRule
+## PrometheusRule
 A PrometheusRule contains the alerting and recording rules that you would usually place in a [Prometheus rule file](https://prometheus.io/docs/prometheus/latest/configuration/recording_rules/).
@@ -22,6 +22,6 @@ For a more fine-grained approach, the `ruleSelector` field on a Prometheus resou
 See the [Prometheus Operator documentation](https://prometheus-operator.dev/docs/user-guides/alerting/) for an example PrometheusRule.
-### Alertmanager Config
+## Alertmanager Config
 See the Rancher docs page on Receivers for an example [Alertmanager config](./receivers.md#example-alertmanager-configs).
@@ -29,6 +29,9 @@ This section assumes familiarity with how monitoring components work together. F
 1. Go to the cluster where you want to create receivers. Click **Monitoring -> Alerting -> AlertManagerConfigs**.
 1. Click **Create**.
 1. Enter a **Name** for the new AlertmanagerConfig. 
 1. Click **Create**.
 1. After creating the AlertManagerConfig, click it to add a receiver.
 1. Click **Add Receiver**.
 1. Enter a **Name** for the receiver.
 1. Configure one or more providers for the receiver. For help filling out the forms, refer to the configuration options below.
@@ -55,11 +58,11 @@ The notification integrations are configured with the `receiver`, which is expla
 By default, AlertManager provides native integration with some receivers, which are listed in [this section.](https://prometheus.io/docs/alerting/latest/configuration/#receiver) All natively supported receivers are configurable through the Rancher UI.
-For notification mechanisms not natively supported by AlertManager, integration is achieved using the [webhook receiver.](https://prometheus.io/docs/alerting/latest/configuration/#webhook_config) A list of third-party drivers providing such integrations can be found [here.](https://prometheus.io/docs/operating/integrations/#alertmanager-webhook-receiver) Access to these drivers, and their associated integrations, is provided through the Alerting Drivers app. Once enabled, configuring non-native receivers can also be done through the Rancher UI.
+For notification mechanisms, such as Telegram, that are not natively supported by AlertManager, integration is achieved using the [webhook receiver.](https://prometheus.io/docs/alerting/latest/configuration/#webhook_config) A list of third-party drivers providing such integrations can be found [here.](https://prometheus.io/docs/operating/integrations/#alertmanager-webhook-receiver) Access to these drivers, and their associated integrations, is provided through the Alerting Drivers app. Once enabled, configuring non-native receivers can also be done through the Rancher UI.
 Currently the Rancher Alerting Drivers app provides access to the following integrations:
- Microsoft Teams, based on the [prom2teams](https://github.com/idealista/prom2teams) driver
+- Microsoft Teams, based on the [prom2teams](https://github.com/idealista/prom2teams) driver.
- SMS, based on the [Sachet](https://github.com/messagebird/sachet) driver
+- Telegram, based on the [Sachet](https://github.com/messagebird/sachet) driver.
 The following types of receivers can be configured in the Rancher UI:
@@ -71,6 +74,7 @@ The following types of receivers can be configured in the Rancher UI:
 - <a href="#custom">Custom</a>
 - <a href="#teams">Teams</a>
 - <a href="#sms">SMS</a>
 - <a href="#telegram">Telegram</a>
 The custom receiver option can be used to configure any receiver in YAML that cannot be configured by filling out the other forms in the Rancher UI.
@@ -132,8 +136,6 @@ Opsgenie Responders:
 | Proxy URL | Proxy for the webhook notification. |
 | Enable Send Resolved Alerts | Whether to send a follow-up notification if an alert has been resolved (e.g. [Resolved] High CPU Usage).    |
 <!-- TODO add info on webhook for teams and sms and link to them -->
 ## Custom
 The YAML provided here will be directly appended to your receiver within the Alertmanager Config Secret.
@@ -211,6 +213,87 @@ url http://rancher-alerting-drivers-sachet.ns-1.svc:9876/alert
 <!-- https://github.com/messagebird/sachet -->
 ## Telegram
 ### Enabling the Telegram Receiver for Rancher Managed Clusters
 The Telegram receiver is not a native receiver. You must enable it before it can be used. You can enable the Telegram receiver for a Rancher-managed cluster by going to the **Apps** page and installing the `rancher-alerting-drivers` app with the **Telegram** option selected:
 1. In the upper left corner, click **☰ > Cluster Management**.
 1. On the **Clusters** page, go to the cluster where you want to install `rancher-alerting-drivers` and click **Explore**.
 1. In the left navigation bar, click on **Apps**.
 1. Click the **Alerting Drivers** app.
 1. Click on **Install**.
 1. In the page that opens next, make sure that **Enable SMS** checkbox is selected. Telegram notifications require you to enable SMS.
 1. Take note of the namespace used as it will be required in a later step.
 ### Test the Configuration by Configuring a PrometheusRule
 To test your Telegram setup, create a **PrometheusRule** that continuously raises alerts. 
 :::caution NOTE
 This rule is intended only to test if Telegram alerts work as expected. Do not leave it on after testing is completed.
 :::
 1. In the left navigation menu, click **Monitoring**.
 1. Click **Advanced**.
 1. Click **PrometheusRules > Create**.
 1. Select a namespace to place the rule in and name the rule appropriately. 
 1. Set the group name to `test`. Use this value later when you create a **Route** in the **AlertManagerConfig**.
 1. Under **Alerting Rules** click **Add**.
 1. Set an appropriate **Alert Name**.
 1. To trigger the alert immediately and continuously, enter the following PromQL Expression: `vector(1)`.
 1. Under **Labels**, click **Add Label**. Enter the key `test` and value `alert`. This key-value pair will also be used later.
 #### Configure an AlertManagerConfig
 Configure an **AlertManagerConfig** to contain the **Receiver** and **Route** configuration for the **PrometheusRule** created above:
 1. Click **Monitoring > Alerting**, and open **AlertManagerConfigs**.
 1. Click **Create**
 #### Create a Receiver in AlertManagerConfig
 1. Choose a namespace from the dropdown and set an appropriate name. 
 1. Click **Create**.
 1. Open the newly created **AlertManagerConfig** and click **⋮ > Edit Config**.
 1. Click **Add Receiver**.
 1. Select **Webhook** from the list on the **Create Receiver in AlertmanagerConfig** page. 
 1. Name the webhook, and click **Add Webhook**. 
 1. In the **Select Webhook Type** dropdown, select **SMS**. This will automatically populate the **Target** field as `http://rancher-alerting-drivers-sachet.cattle-monitoring-system.svc:9876/alert`. If you installed the **Alerting Drivers** in a namespace other than `cattle-monitoring-system`, the target URL will reflect that. 
 1. Click **Create**.
 #### Create a Route in AlertManagerConfig
 1. Click **⋮ > Edit Config**.
 1. Click **Route**.
 1. In the dropdown, select the **Receiver** you just created.
 1. In the **Labels to Group Alerts By** field, type `test`.
 1. Under **Waiting and Intervals**, set **Group Wait** to `1s` and **Group Interval** to `10s`. This triggers frequent alerts. Change the values as appropriate.
 1. Under **Matchers** click **Add Matcher**. Enter `test` in the **Name** field and `alert` in the **Value** field. From the **Match Type** dropdown, select `MatchEqual`.
 1. Click **Save**.
 ### Configuring the Telegram Receiver
 You can configure the Telegram receiver by updating the `rancher-alerting-drivers-sachet` ConfigMap in the `cattle-monitoring-system` namespace. For example, the following is a minimal Telegram receiver configuration:
 ```yaml
 providers:
  telegram:
    token: <your-token-from-telegram>
 receivers:
 - name: 'cattle-monitoring-system/test-amc/prom2tel'
  provider: 'telegram'
  to:
    - '123456789'
 ```
 To obtain a Telegram token, setup a Telegram bot. Refer to the [official Telegram guide](https://core.telegram.org/bots/tutorial) for details.
 After you finish configuring the receiver, [add](#creating-receivers-in-the-rancher-ui) it. 
 Name the receiver `<namespace>/<alertmanagerconfig-name>/<receiver-name>`. Enter `123456789` as a placeholder for the Telegram user ID to send the notifications to. To find your Telegram ID, check [the Telegram userinfo bot](https://telegram.me/userinfobot).
 You should now receive Telegram notifications to the user ID. If you don't receive notifications, please check if there are any errors reported in the Pod for the Deployment `rancher-alerting-drivers-sachet` under the `cattle-monitoring-system` namespace.
 ## Configuring Multiple Receivers
@@ -18,7 +18,7 @@ This section assumes familiarity with how monitoring components work together. F
 :::
-### ServiceMonitors
+## ServiceMonitors
 This pseudo-CRD maps to a section of the Prometheus custom resource configuration. It declaratively specifies how groups of Kubernetes services should be monitored.
@@ -28,7 +28,7 @@ Any Services in your cluster that match the labels located within the ServiceMon
 For more information about how ServiceMonitors work, refer to the [Prometheus Operator documentation.](https://github.com/prometheus-operator/prometheus-operator/blob/master/Documentation/user-guides/running-exporters.md)
-### PodMonitors
+## PodMonitors
 This pseudo-CRD maps to a section of the Prometheus custom resource configuration. It declaratively specifies how group of pods should be monitored.
@@ -89,6 +89,12 @@ We recommend exporting the kubeconfig file so that if Rancher goes down, you can
 ## Impersonation
 :::caution Known Issue
 Service account impersonation (`--as`) used by lower privileged user accounts to remove privileges is not implemented and is a [feature](https://github.com/rancher/rancher/issues/41988) being tracked.
 :::
 Users technically exist only on the upstream cluster. Rancher creates [RoleBindings and ClusterRoleBindings](https://kubernetes.io/docs/reference/access-authn-authz/rbac/#rolebinding-and-clusterrolebinding) that refer to Rancher users, even though there is [no actual User resource](https://kubernetes.io/docs/reference/access-authn-authz/authentication/#users-in-kubernetes) on the downstream cluster.
 When users interact with a downstream cluster through the authentication proxy, there needs to be some entity downstream to serve as the actor for those requests. Rancher creates service accounts to be that entity. Each service account is only granted one permission, which is to **impersonate** the user they belong to. If there was only one service account that could impersonate any user, then it would be possible for a malicious user to corrupt that account and escalate their privileges by impersonating another user. This issue was the basis for a [CVE](https://github.com/rancher/rancher/security/advisories/GHSA-pvxj-25m6-7vqr).
@@ -20,6 +20,8 @@ Each Rancher version is designed to be compatible with a single version of the w
 | Rancher Version | Webhook Version | Availability in Prime | Availability in Community |
 |-----------------|-----------------|-----------------------|---------------------------|
 | v2.9.2          |     v0.5.2      | &check;               | &check;                   |
 | v2.9.1          |     v0.5.1      | &check;               | &check;                   |
 | v2.9.0          |     v0.5.0      | &cross;               | &check;                   |
 ## Why Do We Need It?
@@ -12,7 +12,7 @@ Make sure you configured the correct kubeconfig (for example, `export KUBECONFIG
 Before running the DNS checks, check the [default DNS provider](../../reference-guides/cluster-configuration/rancher-server-configuration/rke1-cluster-configuration.md#default-dns-provider) for your cluster and make sure that [the overlay network is functioning correctly](networking.md#check-if-overlay-network-is-functioning-correctly) as this can also be the reason why DNS resolution (partly) fails.
-### Check if DNS pods are running
+## Check if DNS pods are running
 ```
 kubectl -n kube-system get pods -l k8s-app=kube-dns
@@ -30,7 +30,7 @@ NAME                        READY   STATUS    RESTARTS   AGE
 kube-dns-5fd74c7488-h6f7n   3/3     Running   0          4m13s
 ```
-### Check if the DNS service is present with the correct cluster-ip
+## Check if the DNS service is present with the correct cluster-ip
 ```
 kubectl -n kube-system get svc -l k8s-app=kube-dns
@@ -41,7 +41,7 @@ NAME               TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)         AGE
 service/kube-dns   ClusterIP   10.43.0.10   <none>        53/UDP,53/TCP   4m13s
 ```
-### Check if domain names are resolving
+## Check if domain names are resolving
 Check if internal cluster names are resolving (in this example, `kubernetes.default`), the IP shown after `Server:` should be the same as the `CLUSTER-IP` from the `kube-dns` service.
@@ -132,15 +132,15 @@ command terminated with exit code 1
 Cleanup the alpine DaemonSet by running `kubectl delete ds/dnstest`.
-### CoreDNS specific
+## CoreDNS specific
-#### Check CoreDNS logging
+### Check CoreDNS logging
 ```
 kubectl -n kube-system logs -l k8s-app=kube-dns
 ```
-#### Check configuration
+### Check configuration
 CoreDNS configuration is stored in the configmap `coredns` in the `kube-system` namespace.
@@ -148,7 +148,7 @@ CoreDNS configuration is stored in the configmap `coredns` in the `kube-system`
 kubectl -n kube-system get configmap coredns -o go-template={{.data.Corefile}}
 ```
-#### Check upstream nameservers in resolv.conf
+### Check upstream nameservers in resolv.conf
 By default, the configured nameservers on the host (in `/etc/resolv.conf`) will be used as upstream nameservers for CoreDNS. You can check this file on the host or run the following Pod with `dnsPolicy` set to `Default`, which will inherit the `/etc/resolv.conf` from the host it is running on.
@@ -156,7 +156,7 @@ By default, the configured nameservers on the host (in `/etc/resolv.conf`) will
 kubectl run -i --restart=Never --rm test-${RANDOM} --image=ubuntu --overrides='{"kind":"Pod", "apiVersion":"v1", "spec": {"dnsPolicy":"Default"}}' -- sh -c 'cat /etc/resolv.conf'
 ```
-#### Enable query logging
+### Enable query logging
 Enabling query logging can be done by enabling the [log plugin](https://coredns.io/plugins/log/) in the Corefile configuration in the configmap `coredns`. You can do so by using `kubectl -n kube-system edit configmap coredns` or use the command below to replace the configuration in place:
@@ -166,9 +166,9 @@ kubectl get configmap -n kube-system coredns -o json | sed -e 's_loadbalance_log
 All queries will now be logged and can be checked using the command in [Check CoreDNS logging](#check-coredns-logging).
-### kube-dns specific
+## kube-dns specific
-#### Check upstream nameservers in kubedns container
+### Check upstream nameservers in kubedns container
 By default, the configured nameservers on the host (in `/etc/resolv.conf`) will be used as upstream nameservers for kube-dns. Sometimes the host will run a local caching DNS nameserver, which means the address in `/etc/resolv.conf` will point to an address in the loopback range (`127.0.0.0/8`) which will be unreachable by the container. In case of Ubuntu 18.04, this is done by `systemd-resolved`. We detect if `systemd-resolved` is running, and will automatically use the `/etc/resolv.conf` file with the correct upstream nameservers (which is located at `/run/systemd/resolve/resolv.conf`).
@@ -185,9 +185,9 @@ module.exports = {
              label: 'Latest',
            },
            2.9: {
-              label: 'v2.9 (Preview)',
+              label: 'v2.9',
              path: 'v2.9',
-              banner: 'unreleased'
+              banner: 'none'
            },
            2.8: {
              label: 'v2.8',
@@ -6,7 +6,7 @@ title: API 令牌
 要停用 API 令牌，你可以删除令牌或停用用户账号。
-### 删除令牌
+## 删除令牌
 要删除令牌：
 1. 转到 `https://<Rancher-Server-IP>/v3/tokens`，在 Rancher API 视图中查看包含所有令牌的列表。
@@ -28,7 +28,7 @@ title: API 令牌
 | `drain-node-*` | 用于清空的令牌（由于没有原生 Kubernetes API，我们使用 `kubectl` 来清空） |
-### 在 Kubeconfig 令牌上设置 TTL
+## 在 Kubeconfig 令牌上设置 TTL
 管理员可以在 Kubeconfig 令牌上设置全局存活时间 (time-to-live，TTL)。如需更改默认 kubeconfig TTL，你可以导航到全局设置并将 [`kubeconfig-default-token-ttl-minutes`](#kubeconfig-default-token-ttl-minutes) 设置为所需的持续时间（单位：分钟）。[`kubeconfig-default-token-ttl-minutes`](#kubeconfig-default-token-ttl-minutes) 的默认值为 0，表示令牌永不过期。
@@ -38,17 +38,17 @@ title: API 令牌
 :::
-### 在生成的 Kubeconfig 中禁用令牌
+## 在生成的 Kubeconfig 中禁用令牌
-1. 将 `kubeconfig-generate-token` 设置为 `false`。此设置让 Rancher 不再在用户单击下载 kubeconfig 文件时自动生成令牌。如果停用此设置，生成的 kubeconfig 将引用 [Rancher CLI](../cli-with-rancher/kubectl-utility.md#使用-kubectl-和-kubeconfig-令牌进行-ttl-认证) 来检索集群的短期令牌。当这个 kubeconfig 在客户端（例如 `kubectl`）中使用时，你需要安装 Rancher CLI 来完成登录请求。
+1. 将 `kubeconfig-generate-token` 设置为 `false`。此设置让 Rancher 不再在用户单击下载 kubeconfig 文件时自动生成令牌。如果停用此设置，生成的 kubeconfig 将引用 [Rancher CLI](../reference-guides/cli-with-rancher/kubectl-utility.md#使用-kubectl-和-kubeconfig-令牌进行-ttl-认证) 来检索集群的短期令牌。当这个 kubeconfig 在客户端（例如 `kubectl`）中使用时，你需要安装 Rancher CLI 来完成登录请求。
 2. 将 `kubeconfig-token-ttl-minutes` 设置为所需的时长（单位：分钟）。`kubeconfig-token-ttl-minutes` 默认设置为 960（即 16 小时）。
-### 令牌哈希
+## 令牌哈希
 你可以启用令牌哈希，令牌将使用 SHA256 算法进行单向哈希。这是一个不可逆的操作，一旦启用，此功能将无法禁用。在启用功能或在测试环境中评估之前，建议你先进行备份。
-要启用令牌哈希，请参阅[本节](../../pages-for-subheaders/enable-experimental-features.md)。
+要启用令牌哈希，请参阅[本节](../how-to-guides/advanced-user-guides/enable-experimental-features/enable-experimental-features.md)。
 此功能将影响所有令牌，包括但不限于以下内容：
@@ -56,7 +56,8 @@ title: API 令牌
 - 持有者令牌 API 密钥/调用
 - 内部操作使用的令牌
-### 令牌设置
+## 令牌设置
 以下全局设置会影响 Rancher 令牌的行为：
 | 设置 | 描述 |
@@ -67,20 +68,20 @@ title: API 令牌
 | [`auth-token-max-ttl-minutes`](#auth-token-max-ttl-minutes) | 除了由 [`auth-user-session-ttl-minutes`](#auth-user-session-ttl-minutes) 控制的令牌外，所有令牌的最大 TTL。 |
 | [`kubeconfig-generate-token`](#kubeconfig-generate-token) | 如果为 true，则在用户下载 kubeconfig 时自动生成令牌。 |
-#### auth-user-session-ttl-minutes
+### auth-user-session-ttl-minutes
 存活时间（TTL）（单位：分钟），用于确定用户身份验证会话令牌的到期时间。过期后，用户将需要登录并获取新令牌。此设置不受 [`auth-token-max-ttl-minutes`](#auth-token-max-ttl-minutes) 的影响。会话令牌是在用户登录 Rancher 时创建的。
-#### kubeconfig-default-token-TTL-minutes
+### kubeconfig-default-token-TTL-minutes
 存活时间（TTL）（单位：分钟），用于确定 kubeconfig 令牌的到期时间。令牌过期后，API 将拒绝令牌。此设置的值不能大于 [`auth-token-max-ttl-minutes`](#auth-token-max-ttl-minutes) 的值。此设置适用于在请求的 kubeconfig 文件中生成的令牌，不包括[由 Rancher CLI 生成的](#在生成的-kubeconfig-中禁用令牌)令牌。
 **此设置从 2.6.6 版本开始引入**。
-#### kubeconfig-token-ttl-minutes
+### kubeconfig-token-ttl-minutes
 存活时间（TTL）（单位：分钟），用于确定由 CLI 生成的 kubeconfig 令牌的到期时间。当 [`kubeconfig-generate-token`](#kubeconfig-generate-token) 设为 false 时，则由 CLI 生成令牌。令牌过期后，API 将拒绝令牌。此设置的值不能大于 [`auth-token-max-ttl-minutes`](#auth-token-max-ttl-minutes) 的值。
 **自版本 2.6.6 起已弃用，并将在 2.8.0 中删除。请知悉，此设置将被 [`kubeconfig-default-token-TTL-minutes`](#kubeconfig-default-token-ttl-minutes) 的值替换**。
-#### auth-token-max-ttl-minutes
+### auth-token-max-ttl-minutes
 身份验证令牌的最大生存时间 (TTL)（单位：分钟）。如果用户尝试创建一个 TTL 大于 `auth-token-max-ttl-minutes` 的令牌，Rancher 会将令牌 TTL 设置为 `auth-token-max-ttl-minutes` 的值。身份验证令牌是为验证 API 请求而创建的。
 **2.6.6 版本更改：适用于所有 kubeconfig 令牌和 API 令牌。**
-#### kubeconfig-generate-token
+### kubeconfig-generate-token
-如果设置为 true，则通过 UI 请求的 kubeconfig 将包含一个有效的令牌。如果设置为 false，kubeconfig 将包含一个使用 Rancher CLI 提示用户登录的命令。然后，[CLI 将为用户检索和缓存令牌](../cli-with-rancher/kubectl-utility.md#使用-kubectl-和-kubeconfig-令牌进行-ttl-认证)。
+如果设置为 true，则通过 UI 请求的 kubeconfig 将包含一个有效的令牌。如果设置为 false，kubeconfig 将包含一个使用 Rancher CLI 提示用户登录的命令。然后，[CLI 将为用户检索和缓存令牌](../reference-guides/cli-with-rancher/kubectl-utility.md#使用-kubectl-和-kubeconfig-令牌进行-ttl-认证)。
@@ -27,7 +27,7 @@ API 有自己的用户界面，你可以从 Web 浏览器访问它。这是查
 ## 认证
-API 请求必须包含认证信息。认证是通过 [API 密钥](../user-settings/api-keys.md)使用 HTTP 基本认证完成的。API 密钥可以创建新集群并通过 `/v3/clusters/` 访问多个集群。[集群和项目角色](../../how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/manage-role-based-access-control-rbac/cluster-and-project-roles.md)会应用于这些键，并限制账号可以查看的集群和项目以及可以执行的操作。
+API 请求必须包含认证信息。认证是通过 [API 密钥](../reference-guides/user-settings/api-keys.md)使用 HTTP 基本认证完成的。API 密钥可以创建新集群并通过 `/v3/clusters/` 访问多个集群。[集群和项目角色](../how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/manage-role-based-access-control-rbac/cluster-and-project-roles.md)会应用于这些键，并限制账号可以查看的集群和项目以及可以执行的操作。
 默认情况下，某些集群级别的 API 令牌是使用无限期 TTL（`ttl=0`）生成的。换言之，除非你让令牌失效，否则 `ttl=0` 的 API 令牌永远不会过期。有关如何使 API 令牌失效的详细信息，请参阅 [API 令牌](api-tokens.md)。
@@ -2,11 +2,11 @@
 title: Rancher 弃用的功能
 ---
-### Rancher 的弃用策略是什么？
+## Rancher 的弃用策略是什么？
 我们在支持[服务条款](https://rancher.com/support-maintenance-terms)中发布了官方弃用策略。
-### 在哪里可以找到 Rancher 已弃用的功能？
+## 在哪里可以找到 Rancher 已弃用的功能？
 Rancher 会在 GitHub 上的[发行说明](https://github.com/rancher/rancher/releases)中公布已弃用的功能。请参阅以下补丁版本了解已弃用的功能：
@@ -20,7 +20,6 @@ Rancher 会在 GitHub 上的[发行说明](https://github.com/rancher/rancher/re
 | [2.6.5](https://github.com/rancher/rancher/releases/tag/v2.6.5) | 2022 年 5 月 12 日 |
 | [2.6.6](https://github.com/rancher/rancher/releases/tag/v2.6.6) | 2022 年 6 月 30 日 |
 ## 如果某个功能标记为弃用，我要怎么做？
-### 如果某个功能标记为弃用，我要怎么做？
+如果某个发行版将某功能标记为"Deprecated"（已弃用），该功能仍然可用并受支持，从而允许用户按照常规流程进行升级。在升级到该功能被标记为"已删除"的发行版前，用户/管理员应该计划剥离该功能。对于新部署，我们建议不要使用已弃用的功能。
 如果某个发行版将某功能标记为"Deprecated"（已弃用），该功能仍然可用并受支持，从而允许用户按照常规流程进行升级。在升级到该功能被标记为"已删除"的发行版前，用户/管理员应该计划剥离该功能。对于新部署，我们建议不要使用已弃用的功能。
@@ -6,11 +6,11 @@ title: Rancher 中已弃用的功能
  <link rel="canonical" href="https://ranchermanager.docs.rancher.com/zh/faq/deprecated-features"/>
 </head>
-### Rancher 的弃用策略是什么？
+## Rancher 的弃用策略是什么？
 我们已经在支持的[服务条款](https://rancher.com/support-maintenance-terms)中发布了官方的弃用策略。
-### 在哪里可以了解 Rancher 中已弃用哪些功能？
+## 在哪里可以了解 Rancher 中已弃用哪些功能？
 Rancher 将在 GitHub 上发布的 Rancher 的[发版说明](https://github.com/rancher/rancher/releases)中发布已弃用的功能。有关已弃用的功能，请参阅以下的补丁版本：
@@ -21,6 +21,6 @@ Rancher 将在 GitHub 上发布的 Rancher 的[发版说明](https://github.com/
 | [2.8.1](https://github.com/rancher/rancher/releases/tag/v2.8.1) | 2024 年 1 月 22 日 |
 | [2.8.0](https://github.com/rancher/rancher/releases/tag/v2.8.0) | 2023 年 12 月 6 日 |
-### 当一个功能被标记为弃用我可以得到什么样的预期？
+## 当一个功能被标记为弃用我可以得到什么样的预期？
 当功能被标记为“已弃用”时，它依然可用并得到支持，允许按照常规的流程进行升级。一旦升级完成，用户/管理员应开始计划在升级到标记为已移除的版本之前放弃使用已弃用的功能。对于新的部署，建议不要使用已弃用的功能。
@@ -14,7 +14,7 @@ enable_cri_dockerd: true
 如果你想使用其他容器运行时，Rancher 也提供使用 Containerd 作为默认运行时的，以边缘为中心的 K3s，和以数据中心为中心的 RKE2 Kubernetes 发行版。即使在 Kubernetes 1.24 删除了树内 Dockershim 之后，你也可以通过 Rancher 升级和管理导入的 RKE2 和 K3s Kubernetes 集群。
-### 常见问题
+## 常见问题
 <br/>
@@ -16,7 +16,7 @@ title: 一般常见问题解答
 ## 是否可以使用 Rancher 2.x 管理 Azure Kubernetes 服务？
-是的。请参阅我们的[集群管理]((../how-to-guides/new-user-guides/manage-clusters/manage-clusters.md))指南，了解 AKS 上可用的 Rancher 功能，以及相关的 [AKS 的文档](../getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-aks.md)
+是的。请参阅我们的[集群管理](../how-to-guides/new-user-guides/manage-clusters/manage-clusters.md)指南，了解 AKS 上可用的 Rancher 功能，以及相关的 [AKS 的文档](../getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-aks.md)
 ## Rancher 是否支持 Windows？
@@ -24,7 +24,7 @@ Rancher 支持 Windows Server 1809 容器。有关如何使用 Windows Worker
 ## Rancher 是否支持 Istio？
-Rancher 支持 [Istio](../pages-for-subheaders/istio.md)。
+Rancher 支持 [Istio](../integrations-in-rancher/istio/istio.md)。
 ## Rancher 2.x 是否支持使用 Hashicorp 的 Vault 来存储密文？
@@ -4,11 +4,11 @@ title: 安装和配置 kubectl
 `kubectl` 是一个 CLI 工具，用于运行 Kubernetes 集群相关的命令。Rancher 2.x 中的许多维护和管理任务都需要它。
-### 安装
+## 安装
 请参阅 [kubectl 安装](https://kubernetes.io/docs/tasks/tools/install-kubectl/)将 kubectl 安装到你的操作系统上。
-### 配置
+## 配置
 使用 RKE 创建 Kubernetes 集群时，RKE 会在本地目录中创建一个 `kube_config_cluster.yml`，该文件包含使用 `kubectl` 或 `helm` 等工具连接到新集群的凭证。
@@ -4,20 +4,19 @@ title: 卸载 Rancher
 本文介绍了如果你不再需要 Rancher、不想再由 Rancher 管理集群、或想删除 Rancher Server 需要怎么做。
-
+## 如果 Rancher Server 被删除，下游集群中的工作负载会怎样？
 ### 如果 Rancher Server 被删除，下游集群中的工作负载会怎样？
 如果 Rancher 删除了或无法恢复，Rancher 管理的下游 Kubernetes 集群中的所有工作负载将继续正常运行。
-### 如果删除了 Rancher Server，该如何访问下游集群？
+## 如果删除了 Rancher Server，该如何访问下游集群？
 如果删除了 Rancher，访问下游集群的方式取决于集群的类型和集群的创建方式。总而言之：
 - **注册集群**：集群不受影响，你可以注册集群前的方法访问该集群。
 - **托管的 Kubernetes 集群**：如果你在 Kubernetes 云提供商（例如 EKS、GKE 或 AKS）中创建集群，你可以继续使用提供商的云凭证来管理集群。
- **RKE 集群**：要访问 [RKE 集群](../pages-for-subheaders/launch-kubernetes-with-rancher.md)，集群必须启用了[授权集群端点（authorized cluster endpoint，ACE）](../reference-guides/rancher-manager-architecture/communicating-with-downstream-user-clusters.md#4-授权集群端点)，而且你必须从 Rancher UI 下载了集群的 kubeconfig 文件。RKE 集群默认启用授权集群端点。通过使用此端点，你可以直接使用 kubectl 访问你的集群，而不用通过 Rancher Server 的[认证代理](../reference-guides/rancher-manager-architecture/communicating-with-downstream-user-clusters.md#1-认证代理)进行通信。有关配置 kubectl 以使用授权集群端点的说明，请参阅[使用 kubectl 和 kubeconfig 文件直接访问集群](../how-to-guides/new-user-guides/manage-clusters/access-clusters/use-kubectl-and-kubeconfig.md#直接使用下游集群进行身份验证)。这些集群将使用删除 Rancher 时配置的身份验证快照。
+- **RKE 集群**：要访问 [RKE 集群](../how-to-guides/new-user-guides/launch-kubernetes-with-rancher/launch-kubernetes-with-rancher.md)，集群必须启用了[授权集群端点（authorized cluster endpoint，ACE）](../reference-guides/rancher-manager-architecture/communicating-with-downstream-user-clusters.md#4-授权集群端点)，而且你必须从 Rancher UI 下载了集群的 kubeconfig 文件。RKE 集群默认启用授权集群端点。通过使用此端点，你可以直接使用 kubectl 访问你的集群，而不用通过 Rancher Server 的[认证代理](../reference-guides/rancher-manager-architecture/communicating-with-downstream-user-clusters.md#1-认证代理)进行通信。有关配置 kubectl 以使用授权集群端点的说明，请参阅[使用 kubectl 和 kubeconfig 文件直接访问集群](../how-to-guides/new-user-guides/manage-clusters/access-clusters/use-kubectl-and-kubeconfig.md#直接使用下游集群进行身份验证)。这些集群将使用删除 Rancher 时配置的身份验证快照。
-### 如果我不想再使用 Rancher 了该怎么做？
+## 如果我不想再使用 Rancher 了该怎么做？
 :::note
@@ -25,7 +24,7 @@ title: 卸载 Rancher
 :::
-如果你[在 Kubernetes 集群上安装了 Rancher](../pages-for-subheaders/install-upgrade-on-a-kubernetes-cluster.md)，你可以使用 [Rancher Cleanup](https://github.com/rancher/rancher-cleanup) 工具删除 Rancher。
+如果你[在 Kubernetes 集群上安装了 Rancher](../getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/install-upgrade-on-a-kubernetes-cluster.md)，你可以使用 [Rancher Cleanup](https://github.com/rancher/rancher-cleanup) 工具删除 Rancher。
 在高可用 (HA) 模式下卸载 Rancher 还将删除所有 `helm-operation-*` Pod 和以下应用程序：
@@ -40,7 +39,7 @@ title: 卸载 Rancher
 移除 Rancher 不会影响导入的集群。有关其他集群类型，请参考[移除 Rancher 后访问下游集群](#如果删除了-rancher-server该如何访问下游集群)。
-### 如果我不想 Rancher 管理我的注册集群该怎么办？
+## 如果我不想 Rancher 管理我的注册集群该怎么办？
 如果你在 Rancher UI 中删除了已注册的集群，则该集群将与 Rancher 分离，集群不会发生改变，你可以使用注册集群之前的方法访问该集群。
@@ -52,7 +51,7 @@ title: 卸载 Rancher
 **结果**：注册的集群已与 Rancher 分离，并在 Rancher 外正常运行。
-### 如果我不想 Rancher 管理我的 RKE 集群或托管的 Kubernetes 集群该怎么办？
+## 如果我不想 Rancher 管理我的 RKE 集群或托管的 Kubernetes 集群该怎么办？
 目前，我们没有将这些集群从 Rancher 中分离出来的功能。在这种情况下，“分离”指的是将 Rancher 组件移除出集群，并独立于 Rancher 管理对集群的访问。
@@ -5,10 +5,10 @@ title: 安全
 **是否有强化指南？**
-强化指南现在位于[安全](../pages-for-subheaders/rancher-security.md)部分。
+强化指南现在位于[安全](../reference-guides/rancher-security/rancher-security.md)部分。
 <br/>
 **Rancher Kubernetes 集群 CIS Benchmark 测试的结果是什么？**
-我们已经针对强化的 Rancher Kubernetes 集群运行了 CIS Kubernetes Benchmark 测试。你可以在[安全](../pages-for-subheaders/rancher-security.md)中找到该评估的结果。
+我们已经针对强化的 Rancher Kubernetes 集群运行了 CIS Kubernetes Benchmark 测试。你可以在[安全](../reference-guides/rancher-security/rancher-security.md)中找到该评估的结果。
@@ -2,9 +2,10 @@
 title: 技术
 ---
-### 如何重置管理员密码？
+## 如何重置管理员密码？
 Docker 安装：
 ```
 $ docker exec -ti <container_id> reset-password
 New password for default administrator (user-xxxxx):
@@ -12,6 +13,7 @@ New password for default administrator (user-xxxxx):
 ```
 Kubernetes 安装（Helm）：
 ```
 $ KUBECONFIG=./kube_config_cluster.yml
 $ kubectl --kubeconfig $KUBECONFIG -n cattle-system exec $(kubectl --kubeconfig $KUBECONFIG -n cattle-system get pods -l app=rancher --no-headers | head -1 | awk '{ print $1 }') -c rancher -- reset-password
@@ -19,10 +21,10 @@ New password for default administrator (user-xxxxx):
 <new_password>
 ```
 ## 我删除/停用了最后一个 admin，该如何解决？
 ### 我删除/停用了最后一个 admin，该如何解决？
 Docker 安装：
 ```
 $ docker exec -ti <container_id> ensure-default-admin
 New default administrator (user-xxxxx)
@@ -31,38 +33,40 @@ New password for default administrator (user-xxxxx):
 ```
 Kubernetes 安装（Helm）：
 ```
 $ KUBECONFIG=./kube_config_cluster.yml
 $ kubectl --kubeconfig $KUBECONFIG -n cattle-system exec $(kubectl --kubeconfig $KUBECONFIG -n cattle-system get pods -l app=rancher | grep '1/1' | head -1 | awk '{ print $1 }') -- ensure-default-admin
 New password for default administrator (user-xxxxx):
 <new_password>
 ```
-### 如何启用调试日志记录？
+
 ## 如何启用调试日志记录？
 请参阅[故障排除：日志记录](../troubleshooting/other-troubleshooting-tips/logging.md)。
-### 我的 ClusterIP 不响应 ping，该如何解决？
+## 我的 ClusterIP 不响应 ping，该如何解决？
 ClusterIP 是一个虚拟 IP，不会响应 ping。要测试 ClusterIP 是否配置正确，最好的方法是使用 `curl` 访问 IP 和端口并检查它是否响应。
-### 在哪里管理节点模板？
+## 在哪里管理节点模板？
 打开你的账号菜单（右上角）并选择`节点模板`。
-### 为什么我的四层负载均衡器处于 `Pending` 状态？
+## 为什么我的四层负载均衡器处于 `Pending` 状态？
-四层负载均衡器创建为 `type: LoadBalancer`。Kubernetes 需要一个可以满足这些请求的云提供商或控制器，否则这些请求将永远处于 `Pending` 状态。有关更多信息，请参阅[云提供商](../pages-for-subheaders/set-up-cloud-providers.md)或[创建外部负载均衡器](https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/)。
+四层负载均衡器创建为 `type: LoadBalancer`。Kubernetes 需要一个可以满足这些请求的云提供商或控制器，否则这些请求将永远处于 `Pending` 状态。有关更多信息，请参阅[云提供商](../how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-cloud-providers/set-up-cloud-providers.md)或[创建外部负载均衡器](https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/)。
-### Rancher 的状态存储在哪里？
+## Rancher 的状态存储在哪里？
 - Docker 安装：在 `rancher/rancher` 容器的嵌入式 etcd 中，位于 `/var/lib/rancher`。
 - Kubernetes install：在为运行 Rancher 而创建的 RKE 集群的 etcd 中。
-### 支持的 Docker 版本是如何确定的？
+## 支持的 Docker 版本是如何确定的？
 我们遵循上游 Kubernetes 版本验证过的 Docker 版本。如果需要获取验证过的版本，请查看 Kubernetes 版本 CHANGELOG.md 中的 [External Dependencies](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.10.md#external-dependencies)。
-### 如何访问 Rancher 创建的节点？
+## 如何访问 Rancher 创建的节点？
 你可以转到**节点**视图，然后下载用于访问 Rancher 创建的节点的 SSH 密钥。选择要访问的节点并单击行尾 **⋮** 按钮，然后选择**下载密钥**，如下图所示。
@@ -74,14 +78,14 @@ ClusterIP 是一个虚拟 IP，不会响应 ping。要测试 ClusterIP 是否配
 $ ssh -i id_rsa user@ip_of_node
 ```
-### 如何在 Rancher 中自动化任务 X？
+## 如何在 Rancher 中自动化任务 X？
 UI 由静态文件组成，并根据 API 的响应工作。换言之，UI 中可以执行的每个操作/任务都可以通过 API 进行自动化。有两种方法可以实现这一点：
 * 访问 `https://your_rancher_ip/v3` 并浏览 API 选项。
 * 在使用 UI 时捕获 API 调用（通常使用 [Chrome 开发者工具](https://developers.google.com/web/tools/chrome-devtools/#network)，但你也可以使用其他工具）。
-### 节点的 IP 地址改变了，该如何恢复？
+## 节点的 IP 地址改变了，该如何恢复？
 节点需要配置静态 IP（或使用 DHCP 保留的 IP）。如果节点的 IP 已更改，你必须在集群中删除并重新添加它。删除后，Rancher 会将集群更新为正确的状态。如果集群不再处于 `Provisioning` 状态，则已从集群删除该节点。
@@ -89,11 +93,11 @@ UI 由静态文件组成，并根据 API 的响应工作。换言之，UI 中可
 在集群中移除并清理节点时，你可以将节点重新添加到集群中。
-### 如何将其他参数/绑定/环境变量添加到 Rancher 启动的 Kubernetes 集群的 Kubernetes 组件中？
+## 如何将其他参数/绑定/环境变量添加到 Rancher 启动的 Kubernetes 集群的 Kubernetes 组件中？
 你可以使用集群选项中的[配置文件](../reference-guides/cluster-configuration/rancher-server-configuration/rke1-cluster-configuration.md#rke-集群配置文件参考)选项来添加其他参数/绑定/环境变量。有关详细信息，请参阅 RKE 文档中的[其他参数、绑定和环境变量](https://rancher.com/docs/rke/latest/en/config-options/services/services-extras/)，或浏览 [Cluster.ymls 示例](https://rancher.com/docs/rke/latest/en/example-yamls/)。
-### 如何检查证书链是否有效？
+## 如何检查证书链是否有效？
 使用 `openssl verify` 命令来验证你的证书链：
@@ -134,7 +138,7 @@ subject= /C=GB/ST=England/O=Alice Ltd/CN=rancher.yourdomain.com
 issuer= /C=GB/ST=England/O=Alice Ltd/CN=Alice Intermediate CA
 ```
-### 如何在服务器证书中检查 `Common Name` 和 `Subject Alternative Names`？
+## 如何在服务器证书中检查 `Common Name` 和 `Subject Alternative Names`？
 虽然技术上仅需要 `Subject Alternative Names` 中有一个条目，但在 `Common Name` 和 `Subject Alternative Names` 中都包含主机名可以最大程度地提高与旧版浏览器/应用程序的兼容性。
@@ -152,7 +156,7 @@ openssl x509 -noout -in cert.pem -text | grep DNS
                DNS:rancher.my.org
 ```
-### 为什么节点发生故障时重新调度一个 pod 需要 5 分钟以上的时间？
+## 为什么节点发生故障时重新调度一个 pod 需要 5 分钟以上的时间？
 这是以下默认 Kubernetes 设置的组合导致的：
@@ -171,6 +175,6 @@ Kubernetes 1.13 默认启用 `TaintBasedEvictions` 功能。有关详细信息
   * `default-not-ready-toleration-seconds`：表示 `notReady:NoExecute` 的容忍度的 `tolerationSeconds`，该设置默认添加到还没有该容忍度的 pod。
   * `default-unreachable-toleration-seconds`：表示 `unreachable:NoExecute` 的容忍度的 `tolerationSeconds`，该设置默认添加到还没有该容忍度的 pod。
-### 我可以在 UI 中使用键盘快捷键吗？
+## 我可以在 UI 中使用键盘快捷键吗？
 是的，你可以使用键盘快捷键访问 UI 的大部分内容。要查看快捷方式的概览，请在 UI 任意位置按 `?`。
@@ -2,11 +2,11 @@
 title: 遥测
 ---
-### 什么是遥测？
+## 什么是遥测？
 遥测（Telemetry）收集 Rancher 安装大小、使用的组件版本以及使用功能的汇总信息。Rancher Labs 会使用此信息来改进产品，我们不会与第三方共享此信息。
-### 收集什么信息？
+## 收集什么信息？
 我们不会收集任何识别信息（如用户名、密码或用户资源的名称或地址）。
@@ -20,12 +20,12 @@ title: 遥测
 - 运行的 Rancher 的镜像名称和版本。
 - 此安装的唯一随机标识符。
-### 我可以看到发送的信息吗？
+## 我可以看到发送的信息吗？
 如果启用了遥测，你可以转到 `https://<your rancher server>/v1-telemetry` 查看当前数据。
 如果未启用遥测，则收集数据的进程未运行，因此没有可供查看的内容。
-### 如何打开或关闭它？
+## 如何打开或关闭它？
 完成初始设置后，管理员可以转到 UI `全局`中的`设置`页面，单击**编辑**，然后将 `telemetry-opt` 更改为 `in` 或 `out`。
@@ -8,7 +8,7 @@ title: 在离线环境中升级
 :::
-### Rancher Helm 模板选项
+## Rancher Helm 模板选项
 使用安装 Rancher 时选择的选项来渲染 Rancher 模板。参考下表来替换每个占位符。Rancher 需要配置为使用私有镜像仓库，以便配置所有 Rancher 启动的 Kubernetes 集群或 Rancher 工具。
@@ -21,7 +21,6 @@ title: 在离线环境中升级
 | `<REGISTRY.YOURDOMAIN.COM:PORT>` | 你的私有镜像仓库的 DNS 名称。 |
 | `<CERTMANAGER_VERSION>` | 在 K8s 集群上运行的 cert-manager 版本。 |
 ### 选项 A：使用默认的自签名证书
 ```
@@ -73,7 +73,7 @@ Rancher 是使用 Kubernetes 的 [Helm](https://helm.sh/) 包管理器安装的
 ### 1. 添加 Helm Chart 仓库
-执行 `helm repo add` 命令，以添加包含安装 Rancher 的 Chart 的 Helm Chart 仓库。有关如何选择仓库，以及哪个仓库最适合你的用例，请参见[选择 Rancher 版本](../getting-started/installation-and-upgrade/resources/choose-a-rancher-version.md)。
+执行 `helm repo add` 命令，以添加包含安装 Rancher 的 Chart 的 Helm Chart 仓库。有关如何选择仓库，以及哪个仓库最适合你的用例，请参见[选择 Rancher 版本](../resources/choose-a-rancher-version.md)。
 - Latest：建议用于试用最新功能
   ```
@@ -103,7 +103,7 @@ Rancher Management Server 默认需要 SSL/TLS 配置来保证访问的安全性
 :::note
-如果你想在外部终止 SSL/TLS，请参见[外部负载均衡器的 TLS 终止](../getting-started/installation-and-upgrade/installation-references/helm-chart-options.md#外部-tls-终止)。
+如果你想在外部终止 SSL/TLS，请参见[外部负载均衡器的 TLS 终止](../installation-references/helm-chart-options.md#外部-tls-终止)。
 :::
@@ -180,7 +180,7 @@ ingress-nginx-controller   LoadBalancer   10.3.244.156   35.233.206.34   80:3187
 ## 10. 安装 Rancher Helm Chart
-按照[本页](../../../pages-for-subheaders/install-upgrade-on-a-kubernetes-cluster.md#安装-rancher-helm-chart)的说明安装 Rancher Helm Chart。任何 Kubernetes 发行版上安装的 Rancher 的 Helm 说明都是一样的。
+按照[本页](./install-upgrade-on-a-kubernetes-cluster.md#安装-rancher-helm-chart)的说明安装 Rancher Helm Chart。任何 Kubernetes 发行版上安装的 Rancher 的 Helm 说明都是一样的。
 安装 Rancher 时，使用上一步获取的 DNS 名称作为 Rancher Server 的 URL。它可以作为 Helm 选项传递进来。例如，如果 DNS 名称是 `rancher.my.org`，你需要使用 `--set hostname=rancher.my.org` 选项来运行 Helm 安装命令。
@@ -190,7 +190,7 @@ ingress-nginx-controller   LoadBalancer   10.3.244.156   35.233.206.34   80:3187
 --set ingress.ingressClassName=nginx
 ```
-请参阅[Helm 安装命令](install-upgrade-on-a-kubernetes-cluster.md#5-根据你选择的证书选项通过-helm-安装-rancher)了解你的证书选项。
+请参阅[Helm 安装命令](./install-upgrade-on-a-kubernetes-cluster.md#5-根据你选择的证书选项通过-helm-安装-rancher)了解你的证书选项。
 在 Rancher v2.7.5 中，如果你打算在集群上使用默认的 GKE Ingress 而不启用 VPC 原生的集群模式，则需要设置以下标志：
@@ -75,7 +75,7 @@ Rancher v2.6.4 将 cluster-api 模块从 v0.4.4 升级到 v1.0.2。反过来，c
 1. 在左侧导航栏中，点击 **Rancher 备份 > 还原**。
   :::note
-   如果 Rancher Backups 应用不可见，你需要到 **Apps** 的 Charts 页面中安装应用。详情请参见[此处](../../../how-to-guides/new-user-guides/helm-charts-in-rancher/helm-charts-in-rancher.md#access-charts)。
+   如果 Rancher Backups 应用不可见，你需要到 **Apps** 的 Charts 页面中安装应用。详情请参见[此处](../../../how-to-guides/new-user-guides/helm-charts-in-rancher/helm-charts-in-rancher.md#访问-charts)。
   :::
@@ -4,7 +4,7 @@ title: Rancher Server Kubernetes 集群的问题排查
 本文介绍如何对安装在 Kubernetes 集群上的 Rancher 进行故障排除。
-### 相关命名空间
+## 相关命名空间
 故障排除主要针对以下 3 个命名空间中的对象：
@@ -12,7 +12,7 @@ title: Rancher Server Kubernetes 集群的问题排查
 - `ingress-nginx`：Ingress Controller Pod 和 services。
 - `cert-manager`：`cert-manager` Pod。
-### "default backend - 404"
+## "default backend - 404"
 很多操作都有可能导致 Ingress Controller 无法将流量转发到你的 Rancher 实例。但是大多数情况下都是由错误的 SSL 配置导致的。
@@ -21,7 +21,7 @@ title: Rancher Server Kubernetes 集群的问题排查
 - [Rancher 是否正在运行](#检查-rancher-是否正在运行)
 - [证书的 Common Name（CN）是 "Kubernetes Ingress Controller Fake Certificate"](#证书的-cn-是-kubernetes-ingress-controller-fake-certificate)
-### 检查 Rancher 是否正在运行
+## 检查 Rancher 是否正在运行
 使用 `kubectl` 检查 `cattle-system` 系统命名空间，并查看 Rancher Pod 的状态是否是 **Running**：
@@ -49,7 +49,7 @@ Events:
  Normal   Started                11m   kubelet, localhost  Started container
 ```
-### 检查 Rancher 日志
+## 检查 Rancher 日志
 使用 `kubectl` 列出 Pod：
@@ -66,7 +66,7 @@ pod/rancher-784d94f59b-vgqzh   1/1       Running   0          10m
 kubectl -n cattle-system logs -f rancher-784d94f59b-vgqzh
 ```
-### 证书的 CN 是 "Kubernetes Ingress Controller Fake Certificate"
+## 证书的 CN 是 "Kubernetes Ingress Controller Fake Certificate"
 使用浏览器检查证书的详细信息。如果显示 CN 是 "Kubernetes Ingress Controller Fake Certificate"，则说明读取或颁发 SSL 证书时出现了问题。
@@ -76,7 +76,7 @@ kubectl -n cattle-system logs -f rancher-784d94f59b-vgqzh
 :::
-### 排查 Cert-Manager 颁发的证书（Rancher 或 Let's Encrypt 生成的）问题
+## 排查 Cert-Manager 颁发的证书（Rancher 或 Let's Encrypt 生成的）问题
 `cert-manager` 有 3 部分：
@@ -107,7 +107,7 @@ Events:
  Warning  ErrGetKeyPair  9m (x16 over 19m)   cert-manager  Error getting keypair for CA issuer: secret "tls-rancher" not found
 ```
-### 排查你自己提供的 SSL 证书问题
+## 排查你自己提供的 SSL 证书问题
 你的证书直接应用于 `cattle-system` 命名空间中的 Ingress 对象。
@@ -127,7 +127,7 @@ kubectl -n ingress-nginx logs -f nginx-ingress-controller-rfjrq nginx-ingress-co
 W0705 23:04:58.240571       7 backend_ssl.go:49] error obtaining PEM from secret cattle-system/tls-rancher-ingress: error retrieving secret cattle-system/tls-rancher-ingress: secret cattle-system/tls-rancher-ingress was not found
 ```
-### 没有匹配的 "Issuer"
+## 没有匹配的 "Issuer"
 你所选的 SSL 配置要求在安装 Rancher 之前先安装 Cert-Manager，否则会出现以下错误:
@@ -138,18 +138,18 @@ Error: validation failed: unable to recognize "": no matches for kind "Issuer" i
 在这种情况下，先安装 Cert-Manager，然后再重新安装 Rancher。
-### Canal Pod 显示 READY 2/3
+## Canal Pod 显示 READY 2/3
 此问题的最常见原因是端口 8472/UDP 在节点之间未打开。因此，你可以检查你的本地防火墙、网络路由或安全组。
 解决网络问题后，`canal` Pod 会超时并重启以建立连接。
-### nginx-ingress-controller Pod 显示 RESTARTS
+## nginx-ingress-controller Pod 显示 RESTARTS
 此问题的最常见原因是 `canal` pod 未能建立覆盖网络。参见 [canal Pod 显示 READY `2/3`](#canal-pod-显示-ready-23) 进行排查。
-### Failed to dial to /var/run/docker.sock: ssh: rejected: administratively prohibited (open failed)
+## Failed to dial to /var/run/docker.sock: ssh: rejected: administratively prohibited (open failed)
 此错误的原因可能是：
@@ -171,18 +171,18 @@ $ nc xxx.xxx.xxx.xxx 22
 SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.10
 ```
-### Failed to dial ssh using address [xxx.xxx.xxx.xxx:xx]: Error configuring SSH: ssh: no key found
+## Failed to dial ssh using address [xxx.xxx.xxx.xxx:xx]: Error configuring SSH: ssh: no key found
 `ssh_key_path` 密钥文件无法访问：请确保你已经指定了私钥文件（不是公钥 `.pub`），而且运行 `rke` 命令的用户可以访问该私钥文件。
-### Failed to dial ssh using address [xxx.xxx.xxx.xxx:xx]: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
+## Failed to dial ssh using address [xxx.xxx.xxx.xxx:xx]: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
 `ssh_key_path` 密钥文件不是访问节点的正确文件：请仔细检查，确保你已为节点指定了正确的 `ssh_key_path` 和连接用户。
-### Failed to dial ssh using address [xxx.xxx.xxx.xxx:xx]: Error configuring SSH: ssh: cannot decode encrypted private keys
+## Failed to dial ssh using address [xxx.xxx.xxx.xxx:xx]: Error configuring SSH: ssh: cannot decode encrypted private keys
 如需使用加密的私钥，请使用 `ssh-agent` 来使用密码来加载密钥。如果在运行 `rke` 命令的环境中找到 `SSH_AUTH_SOCK` 环境变量，它将自动用于连接到节点。
-### Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
+## Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
 节点无法通过配置的 `address` 和 `port` 访问。
@@ -22,7 +22,7 @@ title: 功能开关
 - `multi-cluster-management`：允许配置和管理多个 Kubernetes 集群。此标志只能在安装时设置。后续无法启用或禁用它。
 - `rke1-custom-node-cleanup`：清除已删除的 RKE1 自定义节点。建议你启用此标志，以防止已删除的节点尝试重新加入集群。
 - `rke2`：启用配置 RKE2 集群。此标志默认启用。
- `token-hashing`：启用令牌哈希。启用后，会使用 SHA256 算法对现有 Token 和所有新 Token 进行哈希处理。一旦对 Token 进行哈希处理，就无法撤消操作。此标志在启用后无法禁用。有关详细信息，请参阅 [API 令牌](../../../reference-guides/about-the-api/api-tokens.md#令牌哈希)。
+- `token-hashing`：启用令牌哈希。启用后，会使用 SHA256 算法对现有 Token 和所有新 Token 进行哈希处理。一旦对 Token 进行哈希处理，就无法撤消操作。此标志在启用后无法禁用。有关详细信息，请参阅 [API 令牌](../../../api/api-tokens.md#令牌哈希)。
 - `unsupported-storage-drivers`：允许启用非默认启用的存储提供程序和卷插件。有关详细信息，请参阅[允许使用不受支持的存储驱动程序](../../../how-to-guides/advanced-user-guides/enable-experimental-features/unsupported-storage-drivers.md)。
 下表介绍了 Rancher 中功能开关的可用性和默认值。标记为“GA”的功能已普遍可用：
@@ -18,7 +18,7 @@ enable_cri_dockerd: true
 如果你想使用其他容器运行时，Rancher 也提供使用 Containerd 作为默认运行时的，以边缘为中心的 K3s，和以数据中心为中心的 RKE2 Kubernetes 发行版。然后，你就可以通过 Rancher 对导入的 RKE2 和 K3s Kubernetes 集群进行升级和管理。
-### 常见问题
+## 常见问题
 <br/>
@@ -75,7 +75,7 @@ Rancher 的硬件占用空间取决于许多因素，包括：
 - 工作负载数量 (例如： Kubernetes 部署，Fleet 部署)。
 - 使用模式 (例如：主动使用的功能集合，使用频率，并发用户数量).
-由于存在许多可能随时间变化的影响因素，因此此处列出的要求为适合大多数用例的起点。 然而，你的用例可能有不同的要求。 若你需要对于特定场景的咨询，请[联系 Rancher]((https://rancher.com/contact/)) 以获得进一步指导。
+由于存在许多可能随时间变化的影响因素，因此此处列出的要求为适合大多数用例的起点。 然而，你的用例可能有不同的要求。 若你需要对于特定场景的咨询，请[联系 Rancher](https://rancher.com/contact/) 以获得进一步指导。
 特别指出，本页面中的要求基于以下假设的环境提出，包括：
@@ -24,7 +24,7 @@ Docker 安装适用于想要测试 Rancher 的用户。
 选择以下的选项之一：
-### 选项 A：使用 Rancher 默认的自签名证书
+## 选项 A：使用 Rancher 默认的自签名证书
 <details id="option-a">
  <summary>单击展开</summary>
@@ -51,7 +51,7 @@ docker run -d --restart=unless-stopped \
 </details>
-### 选项 B：使用你自己的证书 - 自签名
+## 选项 B：使用你自己的证书 - 自签名
 <details id="option-b">
  <summary>单击展开</summary>
@@ -94,7 +94,7 @@ docker run -d --restart=unless-stopped \
 </details>
-### 选项 C：使用你自己的证书 - 可信 CA 签名的证书
+## 选项 C：使用你自己的证书 - 可信 CA 签名的证书
 <details id="option-c">
  <summary>单击展开</summary>
@@ -21,7 +21,7 @@ Rancher 可以安装在任何 Kubernetes 集群上。为了阅读方便，我们
 - **1 个 DNS 记录**：用于将 URL 映射到负载均衡器。此 DNS 记录将成为 Rancher Server 的 URL，下游集群需要可以访问到这个地址。
 - **私有镜像仓库**，用于将容器镜像分发到你的主机。
-### 1. 配置 Linux 节点
+## 1. 配置 Linux 节点
 这些主机会断开互联网链接，但需要能与你的私有镜像仓库连接。
@@ -29,7 +29,7 @@ Rancher 可以安装在任何 Kubernetes 集群上。为了阅读方便，我们
 如需获取配置 Linux 节点的示例，请参见[在 Amazon EC2 中配置节点](../../../../how-to-guides/new-user-guides/infrastructure-setup/nodes-in-amazon-ec2.md)的教程。
-### 2. 配置外部数据库
+## 2. 配置外部数据库
 K3s 与其他 Kubernetes 发行版不同，在于其支持使用 etcd 以外的数据库来运行 Kubernetes。该功能让 Kubernetes 运维更加灵活。你可以根据实际情况选择合适的数据库。
@@ -45,7 +45,7 @@ K3s 与其他 Kubernetes 发行版不同，在于其支持使用 etcd 以外的
 如需获取配置 K3s 集群数据库的所有可用选项，请参见 [K3s 官方文档](https://rancher.com/docs/k3s/latest/en/installation/datastore/)。
-### 3. 配置负载均衡器
+## 3. 配置负载均衡器
 你还需要设置一个负载均衡器，来将流量重定向到两个节点上的 Rancher 副本。配置后，当单个节点不可用时，继续保障与 Rancher Management Server 的通信。
@@ -68,7 +68,7 @@ K3s 与其他 Kubernetes 发行版不同，在于其支持使用 etcd 以外的
 :::
-### 4. 配置 DNS 记录
+## 4. 配置 DNS 记录
 配置完负载均衡器后，你将需要创建 DNS 记录，以将流量发送到该负载均衡器。
@@ -78,7 +78,7 @@ K3s 与其他 Kubernetes 发行版不同，在于其支持使用 etcd 以外的
 有关设置 DNS 记录以将域流量转发到 Amazon ELB 负载均衡器的指南，请参见 [AWS 官方文档](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-to-elb-load-balancer)。
-### 5. 配置私有镜像仓库
+## 5. 配置私有镜像仓库
 Rancher 支持使用私有镜像仓库进行离线安装。你必须有自己的私有镜像仓库或使用其他方式将容器镜像分发到主机。
@@ -102,21 +102,21 @@ Rancher 支持使用私有镜像仓库进行离线安装。你必须有自己的
 这些节点必须位于同一个区域或数据中心。但是你可以把这些服务器放在不同的可用区。
-### 为什么使用三个节点？
+## 为什么使用三个节点？
 在 RKE 集群中，Rancher Server 的数据存储在 etcd 中。而这个 etcd 数据库在这三个节点上运行。
 为了选举出大多数 etcd 节点认可的 etcd 集群 leader，etcd 数据库需要奇数个节点。如果 etcd 数据库无法选出 leader，etcd 可能会出现[脑裂（split brain）](https://www.quora.com/What-is-split-brain-in-distributed-systems)的问题，此时你需要使用备份恢复集群。如果三个 etcd 节点之一发生故障，其余两个节点可以选择一个 leader，因为它们是 etcd 节点总数的大多数部分。
-### 1. 配置 Linux 节点
+## 1. 配置 Linux 节点
 这些主机会断开互联网链接，但需要能与你的私有镜像仓库连接。
-请确保你的节点满足[操作系统，容器运行时，硬件和网络](../../../../pages-for-subheaders/installation-requirements.md)的常规要求。
+请确保你的节点满足[操作系统，容器运行时，硬件和网络](../../installation-requirements/installation-requirements.md)的常规要求。
 如需获取配置 Linux 节点的示例，请参见[在 Amazon EC2 中配置节点](../../../../how-to-guides/new-user-guides/infrastructure-setup/nodes-in-amazon-ec2.md)的教程。
-### 2. 配置负载均衡器
+## 2. 配置负载均衡器
 你还需要设置一个负载均衡器，来将流量重定向到两个节点上的 Rancher 副本。配置后，当单个节点不可用时，继续保障与 Rancher Management Server 的通信。
@@ -139,7 +139,7 @@ Rancher 支持使用私有镜像仓库进行离线安装。你必须有自己的
 :::
-### 3. 配置 DNS 记录
+## 3. 配置 DNS 记录
 配置完负载均衡器后，你将需要创建 DNS 记录，以将流量发送到该负载均衡器。
@@ -149,7 +149,7 @@ Rancher 支持使用私有镜像仓库进行离线安装。你必须有自己的
 有关设置 DNS 记录以将域流量转发到 Amazon ELB 负载均衡器的指南，请参见 [AWS 官方文档](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-to-elb-load-balancer)。
-### 4. 配置私有镜像仓库
+## 4. 配置私有镜像仓库
 Rancher 支持使用安全的私有镜像仓库进行离线安装。你必须有自己的私有镜像仓库或使用其他方式将容器镜像分发到主机。
@@ -172,15 +172,15 @@ Rancher 支持使用安全的私有镜像仓库进行离线安装。你必须有
 :::
-### 1. 配置 Linux 节点
+## 1. 配置 Linux 节点
 此主机会断开互联网链接，但需要能与你的私有镜像仓库连接。
-请确保你的节点满足[操作系统，容器，硬件和网络](../../../../pages-for-subheaders/installation-requirements.md)的常规安装要求。
+请确保你的节点满足[操作系统，容器，硬件和网络](../../installation-requirements/installation-requirements.md)的常规安装要求。
 如需获取配置 Linux 节点的示例，请参见[在 Amazon EC2 中配置节点](../../../../how-to-guides/new-user-guides/infrastructure-setup/nodes-in-amazon-ec2.md)的教程。
-### 2. 配置私有 Docker 镜像仓库
+## 2. 配置私有 Docker 镜像仓库
 Rancher 支持使用私有镜像仓库在堡垒服务器中进行离线安装。你必须有自己的私有镜像仓库或使用其他方式将容器镜像分发到主机。
@@ -189,5 +189,5 @@ Rancher 支持使用私有镜像仓库在堡垒服务器中进行离线安装。
 </TabItem>
 </Tabs>
-### 后续操作
+## 后续操作
 [收集镜像并发布到你的私有镜像仓库](publish-images.md)
@@ -4,7 +4,7 @@ title: 4. 安装 Rancher
 本文介绍如何在高可用 Kubernetes 安装的离线环境部署 Rancher。离线环境可以是 Rancher Server 离线安装、防火墙后面或代理后面。
-### Rancher 特权访问
+## Rancher 特权访问
 当 Rancher Server 部署在 Docker 容器中时，容器内会安装一个本地 Kubernetes 集群供 Rancher 使用。为 Rancher 的很多功能都是以 deployment 的方式运行的，而在容器内运行容器是需要特权模式的，因此你需要在安装 Rancher 时添加 `--privileged` 选项。
@@ -116,7 +116,7 @@ curl -L -o cert-manager-crd.yaml https://github.com/cert-manager/cert-manager/re
 将获取的 Chart 复制到有权访问 Rancher Server 集群的系统以完成安装。
-##### 1. 安装 Cert-Manager
+#### 1. 安装 Cert-Manager
 使用要用于安装 Chart 的选项来安装 cert-manager。记住要设置 `image.repository` 选项，以从你的私有镜像仓库拉取镜像。此操作会创建一个包含 Kubernetes manifest 文件的 `cert-manager` 目录。
@@ -156,7 +156,8 @@ curl -L -o cert-manager-crd.yaml https://github.com/cert-manager/cert-manager/re
 </details>
-##### 2. 安装 Rancher
+#### 2. 安装 Rancher
 首先，参见[添加 TLS 密文](../../resources/add-tls-secrets.md)发布证书文件，以便 Rancher 和 Ingress Controller 可以使用它们。
 然后，使用 kubectl 为 Rancher 创建命名空间：
@@ -2,13 +2,13 @@
 title: 其他安装方式
 ---
-### 离线安装
+## 离线安装
 按照[以下步骤](air-gapped-helm-cli-install/air-gapped-helm-cli-install.md)在离线环境中安装 Rancher Server。
 离线环境可以是 Rancher Server 离线安装、防火墙后面或代理后面。
-### Docker 安装
+## Docker 安装
 [单节点 Docker 安装](rancher-on-a-single-node-with-docker/rancher-on-a-single-node-with-docker.md)适用于想要测试 Rancher 的用户。你无需使用 Helm 在 Kubernetes 集群上运行 Rancher，你可以使用 `docker run` 命令，把 Rancher Server 组件安装到单个节点上。
@@ -4,7 +4,7 @@ title: 3. 安装 Rancher
 在前文的操作后，你已经有了一个运行的 RKE 集群，现在可以在其中安装 Rancher 了。出于安全考虑，所有到 Rancher 的流量都必须使用 TLS 加密。在本教程中，你将使用 [cert-manager](https://cert-manager.io/)自动颁发自签名证书。在实际使用情况下，你可使用 Let's Encrypt 或自己的证书。
-### 安装 Helm CLI
+## 安装 Helm CLI
 <DeprecationHelm2 />
@@ -16,7 +16,7 @@ chmod +x get_helm.sh
 sudo ./get_helm.sh
 ```
-### 安装 cert-manager
+## 安装 cert-manager
 添加 cert-manager Helm 仓库：
@@ -59,7 +59,7 @@ kubectl rollout status deployment -n cert-manager cert-manager
 kubectl rollout status deployment -n cert-manager cert-manager-webhook
 ```
-### 安装 Rancher
+## 安装 Rancher
 接下来，你可以安装 Rancher 了。首先，添加 Helm 仓库：
@@ -97,7 +97,7 @@ kubectl rollout status deployment -n cattle-system rancher
 :::
-### 其他资源
+## 其他资源
 以下资源可能对安装 Rancher 有帮助：
@@ -12,13 +12,13 @@ title: '1. 配置基础设施'
 这些节点必须位于同一个区域或数据中心。但是你可以把这些服务器放在不同的可用区。
-### 为什么使用三个节点？
+## 为什么使用三个节点？
 在 RKE 集群中，Rancher Server 的数据存储在 etcd 中。而这个 etcd 数据库在这三个节点上运行。
 为了选举出大多数 etcd 节点认可的 etcd 集群 leader，etcd 数据库需要奇数个节点。如果 etcd 数据库无法选出 leader，etcd 可能会出现[脑裂（split brain）](https://www.quora.com/What-is-split-brain-in-distributed-systems)的问题，此时你需要使用备份恢复集群。如果三个 etcd 节点之一发生故障，其余两个节点可以选择一个 leader，因为它们是 etcd 节点总数的大多数部分。
-### 1. 配置 Linux 节点
+## 1. 配置 Linux 节点
 这些主机将通过 HTTP 代理连接到互联网。
@@ -26,7 +26,7 @@ title: '1. 配置基础设施'
 如需获取配置 Linux 节点的示例，请参见[在 Amazon EC2 中配置节点](../../../../how-to-guides/new-user-guides/infrastructure-setup/nodes-in-amazon-ec2.md)的教程。
-### 2. 配置负载均衡器
+## 2. 配置负载均衡器
 你还需要设置一个负载均衡器，来将流量重定向到两个节点上的 Rancher 副本。配置后，当单个节点不可用时，继续保障与 Rancher Management Server 的通信。
@@ -49,7 +49,7 @@ title: '1. 配置基础设施'
 :::
-### 3. 配置 DNS 记录
+## 3. 配置 DNS 记录
 配置完负载均衡器后，你将需要创建 DNS 记录，以将流量发送到该负载均衡器。
@@ -60,5 +60,5 @@ title: '1. 配置基础设施'
 有关设置 DNS 记录以将域流量转发到 Amazon ELB 负载均衡器的指南，请参见 [AWS 官方文档](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-to-elb-load-balancer)。
-### 后续操作
+## 后续操作
 [配置 Kubernetes 集群](install-kubernetes.md)
@@ -4,7 +4,7 @@ title: 证书故障排除
 <DockerSupportWarning />
-### 如何确定我的证书格式是否为 PEM？
+## 如何确定我的证书格式是否为 PEM？
 你可以通过以下特征识别 PEM 格式：
@@ -48,7 +48,7 @@ VWQqljhfacYPgp8KJUJENQ9h5hZ2nSCrI+W00Jcw4QcEdCI8HL5wmg==
 -----END PRIVATE KEY-----
 ```
-### 将 PKCS8 证书密钥转换为 PKCS1
+## 将 PKCS8 证书密钥转换为 PKCS1
 如果你使用的是 PKCS8 证书密钥文件，Rancher 将打印以下日志：
@@ -64,7 +64,7 @@ openssl rsa -in key.pem -out convertedkey.pem
 你可使用 `convertedkey.pem` 作为 Rancher 证书密钥文件。
-### 添加中间证书的顺序是什么？
+## 添加中间证书的顺序是什么？
 添加证书的顺序如下：
@@ -77,7 +77,7 @@ openssl rsa -in key.pem -out convertedkey.pem
 -----END CERTIFICATE-----
 ```
-### 如何验证我的证书链？
+## 如何验证我的证书链？
 你可使用 `openssl` 二进制文件来验证证书链。如果命令的输出以 `Verify return code: 0 (ok)` 结尾（参见以下示例），你的证书链是有效的。`ca.pem` 文件必须与你添加到 `rancher/rancher` 容器中的文件一致。
@@ -73,7 +73,7 @@ docker run -d --restart=unless-stopped \
 使用 [OpenSSL](https://www.openssl.org/) 或其他方法创建自签名证书。
 - 证书文件的格式必须是 PEM。
- 在你的证书文件中，包括链中的所有中间证书。你需要对你的证书进行排序，把你的证书放在最前面，后面跟着中间证书。如需查看示例，请参见[证书故障排除](../getting-started/installation-and-upgrade/other-installation-methods/rancher-on-a-single-node-with-docker/certificate-troubleshooting.md)。
+- 在你的证书文件中，包括链中的所有中间证书。你需要对你的证书进行排序，把你的证书放在最前面，后面跟着中间证书。如需查看示例，请参见[证书故障排除](./certificate-troubleshooting.md)。
 :::
@@ -107,7 +107,7 @@ docker run -d --restart=unless-stopped \
 :::note 先决条件：
 - 证书文件的格式必须是 PEM。
- 在你的证书文件中，包括可信 CA 提供的所有中间证书。你需要对你的证书进行排序，把你的证书放在最前面，后面跟着中间证书。如需查看示例，请参见[证书故障排除](../getting-started/installation-and-upgrade/other-installation-methods/rancher-on-a-single-node-with-docker/certificate-troubleshooting.md)。
+- 在你的证书文件中，包括可信 CA 提供的所有中间证书。你需要对你的证书进行排序，把你的证书放在最前面，后面跟着中间证书。如需查看示例，请参见[证书故障排除](./certificate-troubleshooting.md)。
 :::
@@ -147,7 +147,7 @@ docker run -d --volumes-from rancher-data \
  rancher/rancher:<RANCHER_VERSION_TAG>
 ```
-特权访问是[必须](../../../../pages-for-subheaders/rancher-on-a-single-node-with-docker.md#rancher-特权访问)的。
+特权访问是[必须](./rancher-on-a-single-node-with-docker.md#rancher-特权访问)的。
 </details>
@@ -183,7 +183,7 @@ docker run -d --volumes-from rancher-data \
  rancher/rancher:<RANCHER_VERSION_TAG>
 ```
-特权访问是[必须](../../../../pages-for-subheaders/rancher-on-a-single-node-with-docker.md#rancher-特权访问)的。
+特权访问是[必须](./rancher-on-a-single-node-with-docker.md#rancher-特权访问)的。
 </details>
@@ -218,7 +218,7 @@ docker run -d --volumes-from rancher-data \
  --no-cacerts
 ```
-特权访问是[必须](../../../../pages-for-subheaders/rancher-on-a-single-node-with-docker.md#rancher-特权访问)的。
+特权访问是[必须](./rancher-on-a-single-node-with-docker.md#rancher-特权访问)的。
 </details>
 #### 选项 D：Let's Encrypt 证书
@@ -255,7 +255,7 @@ docker run -d --volumes-from rancher-data \
  --acme-domain <YOUR.DNS.NAME>
 ```
-特权访问是[必须](../../../../pages-for-subheaders/rancher-on-a-single-node-with-docker.md#rancher-特权访问)的。
+特权访问是[必须](./rancher-on-a-single-node-with-docker.md#rancher-特权访问)的。
 </details>
@@ -288,7 +288,7 @@ docker run -d --volumes-from rancher-data \
      <REGISTRY.YOURDOMAIN.COM:PORT>/rancher/rancher:<RANCHER_VERSION_TAG>
 ```
-特权访问是[必须](../../../../pages-for-subheaders/rancher-on-a-single-node-with-docker.md#rancher-特权访问)的。
+特权访问是[必须](./rancher-on-a-single-node-with-docker.md#rancher-特权访问)的。
 </details>
 #### 选项 B：使用你自己的证书 - 自签名
@@ -324,7 +324,7 @@ docker run -d --restart=unless-stopped \
    --privileged \
    <REGISTRY.YOURDOMAIN.COM:PORT>/rancher/rancher:<RANCHER_VERSION_TAG>
 ```
-特权访问是[必须](../../../../pages-for-subheaders/rancher-on-a-single-node-with-docker.md#rancher-特权访问)的。
+特权访问是[必须](./rancher-on-a-single-node-with-docker.md#rancher-特权访问)的。
 </details>
 #### 选项 C：使用你自己的证书 - 可信 CA 签名的证书
@@ -366,7 +366,7 @@ docker run -d --volumes-from rancher-data \
     --privileged
     <REGISTRY.YOURDOMAIN.COM:PORT>/rancher/rancher:<RANCHER_VERSION_TAG>
 ```
-特权访问是[必须](../../../../pages-for-subheaders/rancher-on-a-single-node-with-docker.md#rancher-特权访问)的。
+特权访问是[必须](./rancher-on-a-single-node-with-docker.md#rancher-特权访问)的。
 </details>
 </TabItem>
@@ -6,7 +6,7 @@ Rancher 首次启动时，会为第一个管理员用户随机生成一个密码
 如果你在安装过程中没有使用变量来设置引导密码，则会随机生成引导密码。如需了解使用变量设置引导密码的详情，请参见下文。
-### 在 Helm 安装中指定引导密码
+## 在 Helm 安装中指定引导密码
 Helm 安装的情况下，你可以使用 `.Values.bootstrapPassword` 在 Helm Chart 值中指定引导密码变量。
@@ -16,7 +16,7 @@ Helm 安装的情况下，你可以使用 `.Values.bootstrapPassword` 在 Helm C
 kubectl get secret --namespace cattle-system bootstrap-secret -o go-template='{{ .data.bootstrapPassword|base64decode}}{{ "\n" }}'
 ```
-### 在 Docker 安装中指定引导密码
+## 在 Docker 安装中指定引导密码
 如果 Rancher 是使用 Docker 安装的，你可以通过在 Docker 安装命令中传递 `-e CATTLE_BOOTSTRAP_PASSWORD=password` 来指定引导密码。
@@ -95,7 +95,7 @@ Rancher Helm Chart 版本与 Rancher 版本（即 `appVersion`）对应。添加
 </TabItem>
 <TabItem value="Docker 镜像">
-在执行 [Docker 安装](../../../pages-for-subheaders/rancher-on-a-single-node-with-docker.md)、升级或回滚时，你可以使用 _tags_ 来安装特定版本的 Rancher。
+在执行 [Docker 安装](../other-installation-methods/rancher-on-a-single-node-with-docker/rancher-on-a-single-node-with-docker.md)、升级或回滚时，你可以使用 _tags_ 来安装特定版本的 Rancher。
 ### Server 标签
@@ -2,19 +2,19 @@
 title: 资源
 ---
-### Docker 安装
+## Docker 安装
 [单节点 Docker 安装](../other-installation-methods/rancher-on-a-single-node-with-docker/rancher-on-a-single-node-with-docker.md)适用于想要测试 Rancher 的用户。你无需使用 Helm 在 Kubernetes 集群上运行 Rancher，你可以使用 `docker run` 命令，把 Rancher Server 组件安装到单个节点上。
 由于只有一个节点和一个 Docker 容器，因此，如果该节点发生故障，由于其他节点上没有可用的 etcd 数据副本，你将丢失 Rancher Server 的所有数据。
-### 离线安装
+## 离线安装
 按照[以下步骤](../other-installation-methods/air-gapped-helm-cli-install/air-gapped-helm-cli-install.md)在离线环境中安装 Rancher Server。
 离线环境可以是 Rancher Server 离线安装、防火墙后面或代理后面。
-### 高级选项
+## 高级选项
 安装 Rancher 时，有如下几个可开启的高级选项：每个安装指南中都提供了对应的选项。了解选项详情：
@@ -32,7 +32,7 @@ Rancher 的 Kubernetes 元数据包含 Rancher 用于配置 [RKE 集群](../../h
 - 更改 Rancher 用于同步元数据的 URL。适用于要让 Rancher 从本地同步而不是与 GitHub 同步的情况。这在离线环境下非常有用。
 - 防止 Rancher 自动同步元数据。这可以防止在 Rancher 中使用新的/不受支持的 Kubernetes 版本。
-### 刷新 Kubernetes 元数据
+## 刷新 Kubernetes 元数据
 默认情况下，管理员或具有**管理集群驱动**[全局角色](../../how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/manage-role-based-access-control-rbac/global-permissions.md)的用户，可以刷新 Kubernetes 元数据。
@@ -44,7 +44,7 @@ Rancher 的 Kubernetes 元数据包含 Rancher 用于配置 [RKE 集群](../../h
 你可以将 `refresh-interval-minutes` 设置为 `0`（见下文），将 Rancher 配置为仅在需要时刷新元数据，并在需要时使用此按钮手动执行元数据刷新。
-### 配置元数据同步
+## 配置元数据同步
 :::caution
@@ -70,7 +70,7 @@ RKE 元数据的配置控制 Rancher 同步元数据的频率以及从何处下
 但是，如果你有[离线设置](#离线设置)需求，你需要将 Kubernetes 元数据仓库镜像到 Rancher 可用的位置。然后，你需要更改 URL 来指向 JSON 文件的新位置。
-### 离线设置
+## 离线设置
 Rancher Server 会定期刷新 `rke-metadata-config` 来下载新的 Kubernetes 版本元数据。有关 Kubernetes 和 Rancher 版本的兼容性表，请参阅[服务条款](https://rancher.com/support-maintenance-terms/all-supported-versions/rancher-v2.2.8/)。
@@ -2,11 +2,11 @@
 title: 部署带有 NodePort 的工作负载
 ---
-### 先决条件
+## 先决条件
 你已有一个正在运行的集群，且该集群中有至少一个节点。
-### 1. 部署工作负载
+## 1. 部署工作负载
 你可以开始创建你的第一个 Kubernetes [工作负载](https://kubernetes.io/docs/concepts/workloads/)。工作负载是一个对象，其中包含 pod 以及部署应用所需的其他文件和信息。
@@ -36,11 +36,11 @@ title: 部署带有 NodePort 的工作负载
 <br/>
-### 2. 查看应用
+## 2. 查看应用
 在**工作负载**页面中，点击工作负载下方的链接。如果 deployment 已完成，你的应用会打开。
-### 注意事项
+## 注意事项
 如果使用云虚拟机，你可能无法访问运行容器的端口。这种情况下，你可以使用 `Execute Shell` 在本地主机的 SSH 会话中测试 Nginx。如果可用的话，使用工作负载下方的链接中 `:` 后面的端口号。在本例中，端口号为 `31568`。
@@ -125,11 +125,11 @@ gettingstarted@rancher:~$
 ```
-### 已完成！
+## 已完成！
 恭喜！你已成功通过 NodePort 部署工作负载。
-#### 后续操作
+### 后续操作
 使用完沙盒后，你需要清理 Rancher Server 和集群。详情请参见：
@@ -2,11 +2,11 @@
 title: 部署带有 Ingress 的工作负载
 ---
-### 先决条件
+## 先决条件
 你已有一个正在运行的集群，且该集群中有至少一个节点。
-### 1. 部署工作负载
+## 1. 部署工作负载
 你可以开始创建你的第一个 Kubernetes [工作负载](https://kubernetes.io/docs/concepts/workloads/)。工作负载是一个对象，其中包含 pod 以及部署应用所需的其他文件和信息。
@@ -19,7 +19,7 @@ title: 部署带有 Ingress 的工作负载
 1. 点击 **Deployment**。
 1. 为工作负载设置**名称**。
 1. 在**容器镜像**字段中，输入 `rancher/hello-world`。注意区分大小写。
-1. 在 `Service Type` 点击 **Add Port** 和 `Cluster IP`，并在 **Private Container Port** 字段中输入`80`。你可以将 `Name` 留空或指定名称。通过添加端口，你可以访问集群内外的应用。有关详细信息，请参阅 [Service](../../../pages-for-subheaders/workloads-and-pods.md#services)。
+1. 在 `Service Type` 点击 **Add Port** 和 `Cluster IP`，并在 **Private Container Port** 字段中输入`80`。你可以将 `Name` 留空或指定名称。通过添加端口，你可以访问集群内外的应用。有关详细信息，请参阅 [Service](../../../how-to-guides/new-user-guides/kubernetes-resources-setup/workloads-and-pods/workloads-and-pods.md#services)。
 1. 单击**创建**。
 **结果**：
@@ -27,7 +27,7 @@ title: 部署带有 Ingress 的工作负载
 * 工作负载已部署。此过程可能需要几分钟。
 * 当工作负载完成部署后，它的状态会变为 **Active**。你可以从项目的**工作负载**页面查看其状态。
-### 2. 通过 Ingress 暴露应用
+## 2. 通过 Ingress 暴露应用
 现在应用已启动并运行，你需要暴露应用以让其他服务连接到它。
@@ -53,17 +53,17 @@ title: 部署带有 Ingress 的工作负载
 **结果**：应用分配到了一个 `sslip.io` 地址并暴露。这可能需要一两分钟。
-### 查看应用
+## 查看应用
 在 **Deployments** 页面中，找到你 deployment 的 **endpoint** 列，然后单击一个 endpoint。可用的 endpoint 取决于你添加到 deployment 中的端口配置。如果你看不到随机分配端口的 endpoint，请将你在创建 Ingress 时指定的路径尾附到 IP 地址上。例如，如果你的 endpoint 是 `xxx.xxx.xxx.xxx` 或 `https://xxx.xxx.xxx.xxx`，把它修改为 `xxx.xxx.xxx.xxx/hello` 或 `https://xxx.xxx.xxx.xxx/hello`。
 应用将在另一个窗口中打开。
-#### 已完成！
+### 已完成！
 恭喜！你已成功通过 Ingress 部署工作负载。
-#### 后续操作
+### 后续操作
 使用完沙盒后，你需要清理 Rancher Server 和集群。详情请参见：
@@ -10,14 +10,14 @@ title: 7 层 NGINX 负载均衡器上的 TLS 终止（Docker 安装）
 ## 操作系统，Docker，硬件和网络要求
-请确保你的节点满足常规的[安装要求](../../pages-for-subheaders/installation-requirements.md)。
+请确保你的节点满足常规的[安装要求](../../getting-started/installation-and-upgrade/installation-requirements/installation-requirements.md)。
 ## 安装概要
 ## 1. 配置 Linux 主机
-根据我们的[要求](../../pages-for-subheaders/installation-requirements.md)配置一个 Linux 主机来启动 Rancher Server。
+根据我们的[要求](../../getting-started/installation-and-upgrade/installation-requirements/installation-requirements.md)配置一个 Linux 主机来启动 Rancher Server。
 ## 2. 选择一个 SSL 选项并安装 Rancher
@@ -166,9 +166,7 @@ http {
 ## 后续操作
 - **推荐**：检查单节点[备份](../../how-to-guides/new-user-guides/backup-restore-and-disaster-recovery/back-up-docker-installed-rancher.md)和[恢复](../../how-to-guides/new-user-guides/backup-restore-and-disaster-recovery/restore-docker-installed-rancher.md)。你可能暂时没有需要备份的数据，但是我们建议你在常规使用 Rancher 后创建备份。
- 创建 Kubernetes 集群：[配置 Kubernetes 集群](../../pages-for-subheaders/kubernetes-clusters-in-rancher-setup.md)。
+- 创建 Kubernetes 集群：[配置 Kubernetes 集群](../../how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/kubernetes-clusters-in-rancher-setup.md)。
 <br/>
 ## 常见问题和故障排除
@@ -188,7 +186,7 @@ http {
 ### 离线环境
-如果你访问此页面是为了完成[离线安装](../../pages-for-subheaders/air-gapped-helm-cli-install.md)，则在运行安装命令时，先将你的私有镜像仓库 URL 附加到 Server 标志中。也就是说，在 `rancher/rancher:latest` 前面添加 `<REGISTRY.DOMAIN.COM:PORT>` 和私有镜像仓库 URL。
+如果你访问此页面是为了完成[离线安装](../../getting-started/installation-and-upgrade/other-installation-methods/air-gapped-helm-cli-install/air-gapped-helm-cli-install.md)，则在运行安装命令时，先将你的私有镜像仓库 URL 附加到 Server 标志中。也就是说，在 `rancher/rancher:latest` 前面添加 `<REGISTRY.DOMAIN.COM:PORT>` 和私有镜像仓库 URL。
 **示例**：
@@ -208,7 +206,7 @@ docker run -d --restart=unless-stopped \
  rancher/rancher:latest
 ```
-此操作需要 [privileged 访问](../../pages-for-subheaders/rancher-on-a-single-node-with-docker.md#rancher-特权访问)。
+此操作需要 [privileged 访问](../../getting-started/installation-and-upgrade/other-installation-methods/rancher-on-a-single-node-with-docker/rancher-on-a-single-node-with-docker.md#rancher-特权访问)。
 这个 7 层 NGINX 配置已经在 NGINX 1.13（Mainline）和 1.14（Stable）版本上进行了测试。
@@ -20,7 +20,7 @@ API 审计可以在 Rancher 安装或升级期间启用。
 | 参数 | 描述 |
 | ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| <a id="audit-level"></a>`AUDIT_LEVEL` | `0` - 禁用审计日志（默认）<br /> `1` - 日志事件元数据<br /> `2` - 日志事件元数据和请求体<br /> `3` - 日志事件元数据，请求体和响应体。请求/响应对的每个日志事务都使用同一个的 `auditID`。<br /> 如需了解每个设置记录的日志内容，请参见[审计日志级别](#审核日志级别)。 |
+| `AUDIT_LEVEL` | `0` - 禁用审计日志（默认）<br /> `1` - 日志事件元数据<br /> `2` - 日志事件元数据和请求体<br /> `3` - 日志事件元数据，请求体和响应体。请求/响应对的每个日志事务都使用同一个的 `auditID`。<br /> 如需了解每个设置记录的日志内容，请参见[审计日志级别](#审核日志级别)。 |
 | `AUDIT_LOG_PATH` | Rancher Server API 的日志路径。默认路径：`/var/log/auditlog/rancher-api-audit.log`。你可以将日志目录挂载到主机。<br/><br/>示例：`AUDIT_LOG_PATH=/my/custom/path/`<br/> |
 | `AUDIT_LOG_MAXAGE` | 旧审计日志文件可保留的最大天数。默认为 10 天。 |
 | `AUDIT_LOG_MAXBACKUP` | 保留的审计日志最大文件个数。默认值为 10。 |
@@ -30,7 +30,7 @@ API 审计可以在 Rancher 安装或升级期间启用。
 ### 审核日志级别
-下表介绍了每个 [`AUDIT_LEVEL`](#audit-level) 记录的 API 事务：
+下表介绍了每个 [`AUDIT_LEVEL`](#api-审计日志选项) 记录的 API 事务：
 | `AUDIT_LEVEL` 设置 | 请求元数据 | 请求体 | 响应元数据 | 响应体 |
 | --------------------- | ---------------- | ------------ | ----------------- | ------------- |
@@ -59,7 +59,7 @@ kubectl -n cattle-system logs -f rancher-84d886bdbb-s4s69 rancher-audit-log
 #### 发送审计日志
-你可以为集群启用 Rancher 的内置日志收集和传送功能，将审计日志和其他服务日志发送到支持的 endpoint。详情请参见 [Rancher 工具 - Logging](../../pages-for-subheaders/logging.md)。
+你可以为集群启用 Rancher 的内置日志收集和传送功能，将审计日志和其他服务日志发送到支持的 endpoint。详情请参见 [Rancher 工具 - Logging](../../integrations-in-rancher/logging/logging.md)。
 ## 审计日志示例
@@ -4,7 +4,7 @@ title: 持续交付
 Rancher 中预装的 [Fleet](../../../integrations-in-rancher/fleet/fleet.md) 无法完全禁用。但是，你可以使用 `continuous-delivery` 功能开关来禁用 GitOps 持续交付的 Fleet 功能。
-如需启用或禁用此功能，请参见[启用实验功能主页](../../../pages-for-subheaders/enable-experimental-features.md)中的说明。
+如需启用或禁用此功能，请参见[启用实验功能主页](./enable-experimental-features.md)中的说明。
 | 环境变量键 | 默认值 | 描述 |
 ---|---|---
@@ -4,9 +4,9 @@ title: UI 管理 Istio 虚拟服务和目标规则
 此功能可启动一个 UI，用于管理 Istio 的流量，其中包括创建、读取、更新和删除虚拟服务（Virtual Service）和目标规则（Destination Rule）。
-> **注意**：启用此功能并不会启用 Istio。集群管理员需要[为集群启用 Istio](../../../pages-for-subheaders/istio-setup-guide.md) 才能使用该功能。
+> **注意**：启用此功能并不会启用 Istio。集群管理员需要[为集群启用 Istio](../istio-setup-guide/istio-setup-guide.md) 才能使用该功能。
-如需启用或禁用此功能，请参见[启用实验功能主页](../../../pages-for-subheaders/enable-experimental-features.md)中的说明。
+如需启用或禁用此功能，请参见[启用实验功能主页](./enable-experimental-features.md)中的说明。
 | 环境变量键 | 默认值 | 状态 | 可用于 |
 ---|---|---|---
@@ -11,7 +11,7 @@ title: "在 ARM64 上运行 Rancher（实验性）"
 如果你的节点使用 ARM64 架构，你可以使用以下选项：
 - 在 ARM64 架构的节点上运行 Rancher
-   - 此选项仅适用于 Docker 安装。请知悉，以下安装命令取代了 [Docker 安装链接](../../../pages-for-subheaders/rancher-on-a-single-node-with-docker.md)中的示例：
+   - 此选项仅适用于 Docker 安装。请知悉，以下安装命令取代了 [Docker 安装链接](../../../getting-started/installation-and-upgrade/other-installation-methods/rancher-on-a-single-node-with-docker/rancher-on-a-single-node-with-docker.md)中的示例：
   ```
   # 在最后一行 `rancher/rancher:vX.Y.Z` 中，请务必将 "X.Y.Z" 替换为包含 ARM64 版本的发布版本。例如，如果你的匹配版本是 v2.5.8，请在此行填写 `rancher/rancher:v2.5.8`。
@@ -4,13 +4,14 @@ title: 使用非默认支持的存储驱动
 此功能允许你使用不是默认启用的存储提供商和卷插件。
-如需启用或禁用此功能，请参见[启用实验功能主页](../../../pages-for-subheaders/enable-experimental-features.md)中的说明。
+如需启用或禁用此功能，请参见[启用实验功能主页](./enable-experimental-features.md)中的说明。
 | 环境变量键 | 默认值 | 描述 |
 ---|---|---
 | `unsupported-storage-drivers` | `false` | 启用非默认启用的存储提供商和卷插件。 |
-### 默认启用的持久卷插件
+## 默认启用的持久卷插件
 下表描述了默认启用的存储类型对应的持久卷插件。启用此功能开关时，不在此列表中的任何持久卷插件均被视为实验功能，且不受支持：
 | 名称 | 插件 |
@@ -25,7 +26,8 @@ title: 使用非默认支持的存储驱动
 | 网络文件系统 | `nfs` |
 | hostPath | `host-path` |
-### 默认启用的 StorageClass
+## 默认启用的 StorageClass
 下表描述了默认启用的 StorageClass 对应的持久卷插件。启用此功能开关时，不在此列表中的任何持久卷插件均被视为实验功能，且不受支持：
 | 名称 | 插件 |
@@ -19,11 +19,11 @@ title: 1. 在集群中启用 Istio
 1. 如果你还没有安装 Monitoring 应用，系统会提示你安装 rancher-monitoring。你也可以选择在 Rancher-monitoring 安装上设置选择器或抓取配置选项。
 1. 可选：为 Istio 组件配置成员访问和[资源限制](../../../integrations-in-rancher/istio/cpu-and-memory-allocations.md)。确保你的 Worker 节点上有足够的资源来启用 Istio。
 1. 可选：如果需要，对 values.yaml 进行额外的配置更改。
-1. 可选：通过[覆盖文件](../../../pages-for-subheaders/configuration-options.md#覆盖文件)来添加其他资源或配置。
+1. 可选：通过[覆盖文件](../../../integrations-in-rancher/istio/configuration-options/configuration-options.md#覆盖文件)来添加其他资源或配置。
 1. 单击**安装**。
 **结果**：已在集群级别安装 Istio。
 ## 其他配置选项
-有关配置 Istio 的更多信息，请参阅[配置参考](../../../pages-for-subheaders/configuration-options.md)。
+有关配置 Istio 的更多信息，请参阅[配置参考](../../../integrations-in-rancher/istio/configuration-options/configuration-options.md)。
@@ -19,11 +19,11 @@ title: 2. 在命名空间中启用 Istio
 **结果**：命名空间带有了 `istio-injection=enabled` 标签。默认情况下，部署在此命名空间中的所有新工作负载都将注入 Istio sidecar。
-### 验证是否启用了自动 Istio Sidecar 注入
+## 验证是否启用了自动 Istio Sidecar 注入
 要验证 Istio 是否已启用，请在命名空间中部署一个 hello-world 工作负载。转到工作负载并单击 pod 名称。在**容器**中，你应该能看到 `istio-proxy` 容器。
-### 排除工作负载的 Istio Sidecar 注入
+## 排除工作负载的 Istio Sidecar 注入
 要排除 Istio sidecar 被注入某工作负载，请在工作负载上使用以下注释：
@@ -48,6 +48,6 @@ sidecar.istio.io/inject: “false”
 :::
 ## 后续步骤
 ### 后续步骤
 [使用 Istio Sidecar 添加部署](use-istio-sidecar.md)
@@ -72,5 +72,6 @@ spec:
 **结果**：生成流到该服务的流量时（例如，刷新 Ingress Gateway URL），你可以在 Kiali 流量图中看到流到 `reviews` 服务的流量被平均分配到了 `v1` 和 `v3`。
-### 后续步骤
+## 后续步骤
 [生成和查看流量](generate-and-view-traffic.md)
@@ -19,7 +19,7 @@ title: 3. 使用 Istio Sidecar 添加部署和服务
 等待几分钟，然后工作负载将升级并具有 Istio sidecar。单击它并转到**容器**。你应该能看到该工作负载旁边的 `istio-proxy`。这意味着为工作负载启用了 Istio sidecar。Istio 正在为 Sidecar Envoy 做所有的接线工作。如果你现在在 yaml 中启用它们，Istio 可以自动执行所有功能。
-### 添加部署和服务
+## 添加部署和服务
 以下是在命名空间中添加新 **Deployment** 的几种方法：
@@ -46,7 +46,7 @@ title: 3. 使用 Istio Sidecar 添加部署和服务
 1. 如果你的文件存储在本地集群中，运行 `kubectl create -f <name of service/deployment file>.yaml`。
 1. 或运行 `cat<< EOF | kubectl apply -f -`，将文件内容粘贴到终端，然后运行 `EOF` 来完成命令。
-### 部署和服务示例
+## 部署和服务示例
 接下来，我们为 Istio 文档中的 BookInfo 应用的示例部署和服务添加 Kubernetes 资源：
@@ -87,7 +87,7 @@ Productpage 服务和部署：
 - 一个 `bookinfo-productpage` 的 ServiceAccount。
 - 一个 `productpage-v1` Deployment。
-### 资源 YAML
+## 资源 YAML
 ```yaml
 # Copyright 2017 Istio Authors
@@ -356,5 +356,6 @@ spec:
 ---
 ```
-### 后续步骤
+## 后续步骤
 [设置 Istio Gateway](set-up-istio-gateway.md)
@@ -4,18 +4,18 @@ title: Pod 安全策略
 :::note
-本文介绍的集群选项仅适用于 [Rancher 已在其中启动 Kubernetes 的集群](../../../pages-for-subheaders/launch-kubernetes-with-rancher.md)。
+本文介绍的集群选项仅适用于 [Rancher 已在其中启动 Kubernetes 的集群](../../new-user-guides/launch-kubernetes-with-rancher/launch-kubernetes-with-rancher.md)。
 :::
 你可以在创建项目的时候设置 Pod 安全策略（PSP）。如果在创建项目期间没有为项目分配 PSP，你也随时可以将 PSP 分配给现有项目。
-### 先决条件
+## 先决条件
 - 在 Rancher 中创建 Pod 安全策略。在将默认 PSP 分配给现有项目之前，你必须有一个可分配的 PSP。有关说明，请参阅[创建 Pod 安全策略](../../new-user-guides/authentication-permissions-and-global-configuration/create-pod-security-policies.md)。
 - 将默认 Pod 安全策略分配给项目所属的集群。如果 PSP 还没有应用到集群，你无法将 PSP 分配给项目。有关详细信息，请参阅[将 pod 安全策略添加到集群](../../new-user-guides/manage-clusters/add-a-pod-security-policy.md)。
-### 应用 Pod 安全策略
+## 应用 Pod 安全策略
 1. 在左上角，单击 **☰ > 集群管理**。
 1. 在**集群**页面上，转到需要移动命名空间的集群，然后单击 **Explore**。
@@ -14,7 +14,7 @@ title: 项目资源配额
 Rancher 中的资源配额包含与 [Kubernetes 原生版本](https://kubernetes.io/docs/concepts/policy/resource-quotas/)相同的功能。Rancher 还扩展了资源配额的功能，从而让你将资源配额应用于项目。有关资源配额如何与 Rancher 中的项目一起使用的详细信息，请参阅[此页面](about-project-resource-quotas.md)。
-### 将资源配额应用于现有项目
+## 将资源配额应用于现有项目
 修改资源配额的使用场景如下：
--- a/Show More
+++ b/Show More
Author	SHA1	Message	Date
Billy Tat	50ca0545e3	Merge release/v2.8.8 into main (#1479 ) * 2.8.8 versions table entry * 2.8.8 webhook table entry * 2.8.8 csp adapter entry * 2.8.8 deprecated features entry	2024-09-20 12:39:28 -04:00
Billy TatandSunil Singh	9fd45993e4	Merge release/v2.9.2 into main (#1482 ) * 2.9.2 versions table entry * 2.9.2 webhook table entry * 2.9.2 csp adapter table entry * 2.9.2 deprecated features table entry * Typo Co-authored-by: Sunil Singh <sunil.singh@suse.com> --------- Co-authored-by: Sunil Singh <sunil.singh@suse.com>	2024-09-20 12:39:10 -04:00
Billy Tat	56b73b0135	Merge pull request #1487 from btat/zh-latest-header-levels zh/latest fix header levels	2024-09-19 13:01:47 -07:00
Billy Tat	dc2b84900b	zh/latest fix header levels	2024-09-19 12:05:51 -07:00
Billy Tat	a0739d3569	Merge pull request #1488 from btat/zh-2.8-header-levels zh/2.8 fix header levels	2024-09-19 11:41:34 -07:00
Billy Tat	058e12628e	Merge branch 'main' into zh-2.8-header-levels	2024-09-18 22:58:39 -07:00
Billy Tat	8c8ec320c2	zh/2.8 fix header levels	2024-09-18 22:56:44 -07:00
Billy Tat	52906fbd36	Merge pull request #1486 from btat/zh-2.8-links-pages-for-subheaders zh/2.8: fix links related to old pages-for-subheaders dir and files	2024-09-18 17:07:31 -07:00
Billy Tat	9b42a00a10	Merge pull request #1484 from btat/zh-latest-links-pages-for-subheaders zh latest: fix links related to old pages-for-subheaders dir and files	2024-09-18 15:48:17 -07:00
Billy TatandMarty Hernandez Avedon	ae79d901c3	Update i18n/zh/docusaurus-plugin-content-docs/current/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md Co-authored-by: Marty Hernandez Avedon <martyavedon@gmail.com>	2024-09-18 14:42:59 -07:00
Marty Hernandez Avedon	c869ea69ac	Fix order of headings (#1465 ) * Fix 'title out of sequence' errors fixed Dockershim.md * fixed deprecated-features.md * fixed install-and-configure-kubectl.md * fixed rancher-is-no-longer-needed.md * fixed security.md * fixed technical-items.md + spacing, duplicate section, admonitions * fixed telemetry.md * fixed upgrades.md * fixed upgrade-kubernetes-without-upgrading-rancher.md * fixed air-gapped-upgrades.md * fixed dockershim.md * fixed docker-install-commands.md * fixed install-kubernetes.md * fixed infrastructure-private-registry.md * fixed install-rancher-ha * fixed manage-namespaces and tune-etcd-for-large-installs.md * fixed cis-scans/configuration-reference.md * fixed custom-benchmark.md * fixed supportconfig.md * fixed harvester/overview.md * fixed logging-architecture.md * fixed logging-helm-chart-options.md + rm'd unnecessary annotation title * fixed taints-and-tolerances.md * fixed longhorn/overview.md * fixed neuvector/overview.md * fixed monitoring-and-alerting * fixed rancher-cli.md * fixed cluster-configuration.md * fixed monitoring-v2-configuration/examples.md * fixed servicemonitors-and-podmonitors.md * fixed other-troubleshooting-tips/dns.md	2024-09-18 14:02:55 -04:00
Billy Tat	02db87e946	zh/2.8: fix links related to old pages-for-subheaders dir and files	2024-09-17 22:38:48 -07:00
Billy Tat	662154b2f3	zh latest: fix links related to old pages-for-subheaders dir and files	2024-09-17 21:58:47 -07:00
Billy Tat	9d5db0e3d0	Fix zh/2.8 links	2024-09-17 15:39:45 -07:00
Billy Tat	9f8e1a7a53	Merge pull request #1483 from btat/zh-latest-links Fix zh/latest links	2024-09-17 11:31:25 -07:00
Billy Tat	32ca0e3ce4	Fix zh/latest links	2024-09-17 08:10:18 -07:00
Billy Tat	07ce57faea	Merge pull request #1480 from rancher/revert-1478-cni-pop Revert "2.8.8/2.9.2 update cni stats"	2024-09-16 18:59:06 -07:00
Billy Tat	0f91ef8082	Revert "2.8.8/2.9.2 update cni stats"	2024-09-16 16:37:07 -07:00
Billy Tat	13de70b576	Merge pull request #1478 from btat/cni-pop 2.8.8/2.9.2 update cni stats	2024-09-16 16:26:19 -07:00
Billy Tat	7d5124973e	Merge pull request #1469 from btat/support-matrix-links Add 2.8.7 and 2.9.1 support matrix links	2024-09-16 16:16:06 -07:00
Billy Tat	3686c39346	2.8.8/2.9.2 update cni stats	2024-09-16 14:40:42 -07:00
Billy Tat	44510920e7	Add 2.8.7 and 2.9.1 support matrix links	2024-09-16 14:19:50 -07:00
Sunil Singh	85a88fcafb	Merge pull request #1468 from rancher/dependabot/submodules/dot-github/styles/suse-vale-styleguide-f773efe Bump .github/styles/suse-vale-styleguide from `1701ad8` to `f773efe`	2024-09-16 10:11:26 -07:00
Dharmit ShahandMarty Hernandez Avedon	86a9be9d39	Add Telegram receiver docs (#1408 ) * Add Telegram receiver docs Signed-off-by: Dharmit Shah <dharmit.shah@suse.com> * Apply suggestions from martyav's review Co-authored-by: Marty Hernandez Avedon <marty.avedon@suse.com> * Undo removal of SMS receiver documentation Signed-off-by: Dharmit Shah <dharmit.shah@suse.com> * Apply suggestions from martyav's second review Co-authored-by: Marty Hernandez Avedon <marty.avedon@suse.com> * Apply suggestions from martyav's third review Co-authored-by: Marty Hernandez Avedon <marty.avedon@suse.com> * versioned for v2.9 * versioned for v2.8 + rm outdated comment --------- Signed-off-by: Dharmit Shah <dharmit.shah@suse.com> Co-authored-by: Marty Hernandez Avedon <marty.avedon@suse.com>	2024-09-16 13:07:24 -04:00
Yiannis Triantafyllopoulos	785d49c44d	docs: Add missing EKS permission (#1467 )	2024-09-16 13:07:00 -04:00
dependabot[bot]	c5d8c4ff54	Bump .github/styles/suse-vale-styleguide from `1701ad8` to `f773efe` Bumps [.github/styles/suse-vale-styleguide](https://github.com/openSUSE/suse-vale-styleguide) from `1701ad8` to `f773efe`. - [Release notes](https://github.com/openSUSE/suse-vale-styleguide/releases) - [Commits](https://github.com/openSUSE/suse-vale-styleguide/compare/1701ad82d0da679f2e8943c877722923adb2411b...f773efe265a8aa99ee6f9ebd0decd28ec23dc161) --- updated-dependencies: - dependency-name: ".github/styles/suse-vale-styleguide" dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>	2024-09-16 16:14:38 +00:00
Yiannis Triantafyllopoulos	554e0d338c	docs: Add EBS CSI Driver permissions to 2.9 (#1454 ) * docs: Add EBS CSI Driver permissions to 2.9 * docs: Adjust wording and keep 2.9 and latest in sync	2024-09-13 15:38:35 -04:00
Artem Sadovskyi	ed271e1eb1	Fixing an ordered list in `Setting up Infrastructure for a High Availability RKE2 Kubernetes Cluster` doc (#1461 ) * docs: typo in order * docs: mirroring the changes in `/versioned_docs/version-2.9`	2024-09-13 14:36:20 -04:00
Billy Tat	d89af44ad3	Merge pull request #1459 from kourosh7/main Update rollbacks.md	2024-09-10 14:00:27 -07:00
Kourosh Maneshni	79f1c8db65	Update rollbacks.md remove extra text	2024-09-10 13:22:36 -07:00
Billy Tat	3562f042a9	Merge pull request #1457 from sunilarjun/capi-update Updating CAPI Page	2024-09-10 13:16:17 -07:00
Kourosh Maneshni	f96b09c6fd	Update rollbacks.md remove unnecessary path in section `Step 2`	2024-09-10 13:03:51 -07:00
Sunil Singh	c507ddc1be	Updating the phrasing to with link to concept definition in Kubernetes docs. The CAPI Operator is not a Rancher Extension currently. Signed-off-by: Sunil Singh <sunil.singh@suse.com>	2024-09-10 09:30:41 -07:00
gunamata	10197cb117	Merge pull request #1450 from gunamata/suse-observability-overview Added a intro page for SUSE Observability	2024-08-29 15:05:12 -07:00
Gunasekhar Matamalam	3b62acfa4c	Minor change based on the PR review feedback Signed-off-by: Gunasekhar Matamalam <gunasekhar.matamalam@suse.com>	2024-08-29 08:36:24 -07:00
gunamataandMarty Hernandez Avedon	e19ebe2165	Update docs/integrations-in-rancher/suse-observability/suse-observability.md Co-authored-by: Marty Hernandez Avedon <marty.avedon@suse.com>	2024-08-29 08:31:47 -07:00
Gunasekhar Matamalam	6afb686967	Added a intro page for SUSE Observability Signed-off-by: Gunasekhar Matamalam <gunasekhar.matamalam@suse.com>	2024-08-28 14:31:35 -07:00
Billy Tat	9cb79db3db	Merge pull request #1385 from mallardduck/bro-docs-fix [2.9.1][2.8-Next1] Add info about Private Registry Credentials covering backup labels	2024-08-26 16:37:52 -07:00
Billy Tat	3d868453d3	Merge pull request #1446 from rancher/release/v2.8 Merge release/v2.8 into main	2024-08-26 16:36:13 -07:00
Billy Tat	07741dfc48	Merge pull request #1445 from rancher/release/v2.9 Merge release/v2.9 into main	2024-08-26 13:25:37 -07:00
Sunil Singh	04d996984f	Merge pull request #1447 from sunilarjun/v2.9.1-impersonation V2.9.1 impersonation - v2.6 addition	2024-08-26 12:41:04 -07:00
Sunil Singh	a025bee29f	Merge branch 'rancher:main' into v2.9.1-impersonation	2024-08-26 11:32:52 -07:00
Sunil Singh	5608d3a7e9	Adding note to v2.6 Signed-off-by: Sunil Singh <sunil.singh@suse.com>	2024-08-26 11:29:54 -07:00
Sunil Singh	bd3447eec5	Merge pull request #1444 from sunilarjun/v2.9.1-impersonation [2.9.1] Impersonation - Known Issue Section	2024-08-26 10:56:17 -07:00
Sunil Singh	c4802f036d	Editing Known Issues to singular Signed-off-by: Sunil Singh <sunil.singh@suse.com>	2024-08-26 09:37:35 -07:00
Billy Tat	dadc85b0f4	Merge pull request #1437 from martyav/aug-2024-release-cni-table [v2.9.1][v2.8.7] Aug 2024 CNI popularity update	2024-08-26 09:21:14 -07:00
Billy Tat	34a3c15409	Merge pull request #1434 from martyav/2.9.1-versions-table [v2.9.1] Update versions table	2024-08-26 09:19:55 -07:00
Billy Tat	ac40bb0ea1	Merge pull request #1433 from martyav/2.8.7-versions-table [v2.8.7] Update versions table	2024-08-26 09:19:26 -07:00
Billy Tat	1b61165bfd	Merge pull request #1435 from martyav/2.8.7-rancher-webhook [v2.8.7] Update Webhook Table	2024-08-26 09:17:50 -07:00
Billy Tat	589363b3bf	Merge pull request #1436 from martyav/2.9.1-rancher-webhook [v2.9.1] Update Webhook Table	2024-08-26 09:16:53 -07:00
Billy Tat	6b5c953747	Merge pull request #1438 from martyav/2.8.7-csp-table [v2.8.7] Update CSP Adapter Table	2024-08-26 09:15:46 -07:00
Billy Tat	1ce86b0926	Merge pull request #1439 from martyav/2.9.1-csp-table [v2.9.1] Update CSP Adapter Table	2024-08-26 09:13:50 -07:00
Sunil Singh	a2d2a88054	Adding in known issues warning to Impersonation section for v2.9.1. Signed-off-by: Sunil Singh <sunil.singh@suse.com>	2024-08-26 09:05:31 -07:00
Billy Tat	e317ba5076	Merge pull request #1440 from martyav/2.8.7-deprecations-table [v2.8.7] Update Deprecations Table	2024-08-26 09:01:58 -07:00
Billy Tat	d46b6efe22	Merge pull request #1441 from martyav/2.9.1-deprecations-table [v2.9.1] Update Deprecations Table	2024-08-26 09:01:17 -07:00
Marty Hernandez AvedonandSunil Singh	7df7b91fc4	Apply suggestions from code review Co-authored-by: Sunil Singh <sunil.singh@suse.com>	2024-08-26 11:38:36 -04:00
Marty Hernandez Avedon Dharmit Shah Billy Tat	ea245e3f5b	[v2.8.7] Update from main to keep working branch PRs less messy to review (#1443 ) * Use crds.enabled to install cert-manager Signed-off-by: Dharmit Shah <dharmit.shah@suse.com> * versioned * reverted changes to earliest versions and slightly modified comment * spacing issue --------- Signed-off-by: Dharmit Shah <dharmit.shah@suse.com> Co-authored-by: Dharmit Shah <dharmit.shah@suse.com> Co-authored-by: Billy Tat <btat@suse.com>	2024-08-26 10:03:09 -04:00
Marty Hernandez Avedon Dharmit Shah Billy Tat	db25cc87a5	[v2.9.1] Update from main to keep working branch PRs less messy to review (#1442 ) * Use crds.enabled to install cert-manager Signed-off-by: Dharmit Shah <dharmit.shah@suse.com> * versioned * reverted changes to earliest versions and slightly modified comment * spacing issue --------- Signed-off-by: Dharmit Shah <dharmit.shah@suse.com> Co-authored-by: Dharmit Shah <dharmit.shah@suse.com> Co-authored-by: Billy Tat <btat@suse.com>	2024-08-26 10:03:00 -04:00
martyav	a7e5e2b9cd	consistently using 3 char month	2024-08-26 08:10:10 -04:00
martyav	8040234882	[v2.8.7] Update Deprecations Table	2024-08-26 08:08:51 -04:00
martyav	8a7de06bb8	[v2.9.1] Update Deprecations Table	2024-08-26 08:06:39 -04:00
martyav	93a4f79512	[v2.9.1] Update CSP Adapter Table	2024-08-26 07:33:42 -04:00
martyav	7d51fdb720	[v2.8.7] Update CSP Adapter Table	2024-08-26 07:31:00 -04:00
martyav	16a44f3fab	[v2.9.1][v2.8.6] Aug 2024 CNI popularity update	2024-08-26 07:04:38 -04:00
martyav	382447e1e1	[v2.9.1] Update Webhook Table	2024-08-26 06:49:21 -04:00
martyav	8d50cb4cb8	[v2.8.7] Update Webhook Table	2024-08-26 06:47:17 -04:00
martyav	304fbc7944	Update versions table - v2.8.7	2024-08-26 06:28:32 -04:00
martyav	bf382897c9	Update versions table - v2.9.1	2024-08-23 16:53:51 -04:00
Billy Tat	9b7d9595f8	Merge pull request #1425 from dharmit/crds.enabled Use crds.enabled to install cert-manager	2024-08-19 13:09:38 -07:00
martyav	5afadf201c	spacing issue	2024-08-19 14:23:37 -04:00
martyav	7f02d2bca2	reverted changes to earliest versions and slightly modified comment	2024-08-19 14:01:01 -04:00
Billy Tat	3ab49d575a	Merge pull request #1430 from rancher/valaparthvi-patch-1 Remove extra double quote from the code	2024-08-16 14:11:41 -07:00
martyav	60e77489ca	versioning	2024-08-16 14:09:17 -04:00
Parthvi Vala	cd6b09a947	Update install-kubernetes.md	2024-08-16 15:06:14 +05:30
Parthvi Vala	94ce568974	Update install-kubernetes.md	2024-08-16 15:01:21 +05:30
Chris Wayne martyav Billy Tat	fd780d0cfb	Update dockershim.md (#1426 ) * Update dockershim.md * versioning * Add reference to replatforming guide --------- Co-authored-by: martyav <marty.avedon@suse.com> Co-authored-by: Billy Tat <btat@suse.com>	2024-08-15 11:27:12 -04:00
Billy Tat	c72420642a	Merge pull request #1414 from rancher/rke2-nodes-incorrect Update ha-rke2-kubernetes-cluster.md	2024-08-14 10:51:41 -07:00
martyav	0c56e643ad	versioned	2024-08-13 10:47:47 -04:00
Billy Tat	632569305c	Merge pull request #1427 from rancher/dependabot/submodules/dot-github/styles/suse-vale-styleguide-1701ad8 Bump .github/styles/suse-vale-styleguide from `7267e53` to `1701ad8`	2024-08-08 22:46:30 -07:00
dependabot[bot]	dd6193ab30	Bump .github/styles/suse-vale-styleguide from `7267e53` to `1701ad8` Bumps [.github/styles/suse-vale-styleguide](https://github.com/openSUSE/suse-vale-styleguide) from `7267e53` to `1701ad8`. - [Release notes](https://github.com/openSUSE/suse-vale-styleguide/releases) - [Commits](https://github.com/openSUSE/suse-vale-styleguide/compare/7267e538abe62921af2b422b937a1f80e8b5f6f1...1701ad82d0da679f2e8943c877722923adb2411b) --- updated-dependencies: - dependency-name: ".github/styles/suse-vale-styleguide" dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>	2024-08-08 17:17:03 +00:00
Dharmit Shah	1ac9342705	Use crds.enabled to install cert-manager Signed-off-by: Dharmit Shah <dharmit.shah@suse.com>	2024-08-08 17:55:20 +05:30
Billy Tat	c9e51f3940	Merge pull request #1423 from rancher/dependabot/submodules/dot-github/styles/suse-vale-styleguide-7267e53 Bump .github/styles/suse-vale-styleguide from `037b0e6` to `7267e53`	2024-08-06 11:31:27 -07:00
dependabot[bot]	0b50813ef4	Bump .github/styles/suse-vale-styleguide from `037b0e6` to `7267e53` Bumps [.github/styles/suse-vale-styleguide](https://github.com/openSUSE/suse-vale-styleguide) from `037b0e6` to `7267e53`. - [Release notes](https://github.com/openSUSE/suse-vale-styleguide/releases) - [Commits](https://github.com/openSUSE/suse-vale-styleguide/compare/037b0e6c65ed1d76abbe87afce3109affb92d122...7267e538abe62921af2b422b937a1f80e8b5f6f1) --- updated-dependencies: - dependency-name: ".github/styles/suse-vale-styleguide" dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>	2024-08-06 17:25:12 +00:00
Billy Tat	02c1192494	Merge pull request #1422 from btat/vale-dependabot Configure dependabot for vale rules	2024-08-02 15:53:07 -07:00
Sunil Singh	c81ab8ad1b	Merge pull request #1421 from sunilarjun/sync-glossary-v2.9 Re-syncing Glossary - v2.9 Docs/Versioned Sidebars	2024-08-02 15:40:08 -07:00
Billy Tat	c2f2645af9	Merge pull request #1420 from btat/vale-dependency Update suse-vale-styleguide dependency	2024-08-02 13:56:31 -07:00
Sunil Singh	25450ce3f0	Fixing whitespace after review. Signed-off-by: Sunil Singh <sunil.singh@suse.com>	2024-08-02 13:16:09 -07:00
martyav	58d5735ea5	versioning	2024-08-02 14:59:52 -04:00
Sunil Singh	ceba62a306	Resyncing Glossary file with v2.9 docs and resyncing versioned sidebars that were missing the glossary field. Signed-off-by: Sunil Singh <sunil.singh@suse.com>	2024-08-02 11:56:25 -07:00
Billy Tat	52d6c14efb	Update suse-vale-styleguide dependency Reference rules from /common	2024-08-02 10:07:54 -07:00
Billy Tat	df9d7ab0a8	Merge pull request #1417 from rancher/martyav-update-readme-for-new-latest Update README.md concerning latest minor version	2024-08-01 16:23:26 -07:00
Billy Tat	cfe40b0a86	Configure dependabot for vale rules	2024-08-01 16:19:54 -07:00
Billy Tat	bb75ae1765	Merge pull request #1419 from btat/ci-ignore-readme Update workflow conditions	2024-08-01 16:06:59 -07:00
Marty Hernandez AvedonandBilly Tat	7400482b35	Update README.md Co-authored-by: Billy Tat <btat@suse.com>	2024-08-01 18:45:31 -04:00
Billy Tat	28617e4be1	Merge pull request #1418 from btat/api-deadspace Remove white space from API ref page	2024-08-01 15:43:10 -07:00
Billy Tat	7370fefe3c	Update workflow conditions - Don't run for README changes - Run style and test deploy for all branches	2024-08-01 15:21:19 -07:00
Billy Tat	a0f600a998	Merge pull request #1416 from sunilarjun/remove-preview Removing Preview/Banner - v2.9 Docs	2024-08-01 15:04:17 -07:00
Billy Tat	6b36d00b9b	Remove white spacee	2024-08-01 14:58:32 -07:00
Marty Hernandez Avedon	3fde374c30	Update README.md concerning latest minor version v2.9 just got released.	2024-08-01 16:12:22 -04:00
Sunil Singh	b737561d7b	Removing Preview label and banner for v2.9. Signed-off-by: Sunil Singh <sunil.singh@suse.com>	2024-08-01 12:37:43 -07:00
dkeightley	65d21cfc40	Update ha-rke2-kubernetes-cluster.md	2024-07-31 17:18:17 +12:00
Dan Pock	011085ac2d	Sync versioned docs pages	2024-07-19 20:05:09 -04:00
DanandMarty Hernandez Avedon	6fd409221d	Update docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/global-default-private-registry.md Co-authored-by: Marty Hernandez Avedon <marty.avedon@suse.com>	2024-07-19 15:06:43 -04:00
DanandMarty Hernandez Avedon	1e93509c84	Update docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/global-default-private-registry.md Co-authored-by: Marty Hernandez Avedon <marty.avedon@suse.com>	2024-07-19 13:32:39 -04:00
DanandMarty Hernandez Avedon	0ca00b121d	Update docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/global-default-private-registry.md Co-authored-by: Marty Hernandez Avedon <marty.avedon@suse.com>	2024-07-19 13:32:10 -04:00
DanandMarty Hernandez Avedon	9ae6f022fc	Update docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/global-default-private-registry.md Co-authored-by: Marty Hernandez Avedon <marty.avedon@suse.com>	2024-07-19 13:27:30 -04:00
DanandMarty Hernandez Avedon	ee9876f04a	Update versioned_docs/version-2.8/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/global-default-private-registry.md Co-authored-by: Marty Hernandez Avedon <marty.avedon@suse.com>	2024-07-19 13:27:23 -04:00
DanandMarty Hernandez Avedon	45bf343dba	Update versioned_docs/version-2.8/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/global-default-private-registry.md Co-authored-by: Marty Hernandez Avedon <marty.avedon@suse.com>	2024-07-19 13:26:45 -04:00
DanandMarty Hernandez Avedon	38a442100c	Update versioned_docs/version-2.8/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/global-default-private-registry.md Co-authored-by: Marty Hernandez Avedon <marty.avedon@suse.com>	2024-07-19 13:26:26 -04:00
DanandMarty Hernandez Avedon	6112a7b128	Update versioned_docs/version-2.8/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/global-default-private-registry.md Co-authored-by: Marty Hernandez Avedon <marty.avedon@suse.com>	2024-07-19 13:25:49 -04:00
Dan Pock	bee7f2e892	Clarify the backup in question is BRO	2024-07-18 12:37:18 -04:00
Dan Pock	bd87f0973b	Add info about Private Registry Credentials covering backup labels	2024-07-18 11:32:44 -04:00