Remove unsupported front matter fields

2026-09-26 13:08:11 +00:00 · 2022-09-23 10:11:24 -07:00
parent 5b064e6548
commit c390289797
1553 changed files with 871 additions and 4500 deletions
@@ -1,12 +1,5 @@
 ---
 title: Docker Install with TLS Termination at Layer-7 NGINX Load Balancer
-weight: 252
-aliases:
-  - /rancher/v2.5/en/installation/single-node/single-node-install-external-lb/
-  - /rancher/v2.5/en/installation/other-installation-methods/single-node-docker/single-node-install-external-lb
-  - /rancher/v2.5/en/installation/options/single-node-install-external-lb
-  - /rancher/v2.5/en/installation/single-node-install-external-lb
-  - /rancher/v2.x/en/installation/resources/advanced/single-node-install-external-lb/
 ---

 For development and testing environments that have a special requirement to terminate TLS/SSL at a load balancer instead of your Rancher Server container, deploy Rancher and configure a load balancer to work with it conjunction.
@@ -1,10 +1,5 @@
 ---
 title: Enabling the API Audit Log to Record System Events
-weight: 4
-aliases:
-  - /rancher/v2.5/en/installation/options/api-audit-log/
-  - /rancher/v2.5/en/installation/api-auditing
-  - /rancher/v2.x/en/installation/resources/advanced/api-audit-log/
 ---

 You can enable the API audit log to record the sequence of system events initiated by individual users. You can know what happened, when it happened, who initiated it, and what cluster it affected. When you enable this feature, all requests to the Rancher API and all responses from it are written to a log.
@@ -1,8 +1,5 @@
 ---
 title: Opening Ports with firewalld
-weight: 1
-aliases:
-  - /rancher/v2.x/en/installation/resources/advanced/firewall/
 ---

 > We recommend disabling firewalld. For Kubernetes 1.19.x and higher, firewalld must be turned off.
@@ -1,9 +1,5 @@
 ---
 title: Tuning etcd for Large Installations
-weight: 2
-aliases:
-  - /rancher/v2.5/en/installation/options/etcd
-  - /rancher/v2.x/en/installation/resources/advanced/etcd/
 ---

 When running larger Rancher installations with 15 or more clusters it is recommended to increase the default keyspace for etcd from the default 2GB. The maximum setting is 8GB and the host should have enough RAM to keep the entire dataset in memory. When increasing this value you should also increase the size of the host. The keyspace size can also be adjusted in smaller installations if you anticipate a high rate of change of pods during the garbage collection interval.
@@ -1,9 +1,5 @@
 ---
 title: UI for Istio Virtual Services and Destination Rules
-weight: 2
-aliases:
-  - /rancher/v2.5/en/installation/options/feature-flags/istio-virtual-service-ui
-  - /rancher/v2.x/en/installation/resources/feature-flags/istio-virtual-service-ui/
 ---

 This feature enables a UI that lets you create, read, update and delete virtual services and destination rules, which are traffic management features of Istio.
@@ -1,9 +1,5 @@
 ---
 title: "Running on ARM64 (Experimental)"
-weight: 3
-aliases:
-  - /rancher/v2.5/en/installation/options/arm64-platform
-  - /rancher/v2.x/en/installation/resources/advanced/arm64-platform/
 ---

 > **Important:**
@@ -1,9 +1,5 @@
 ---
 title: Allow Unsupported Storage Drivers
-weight: 1
-aliases:
-  - /rancher/v2.5/en/installation/options/feature-flags/enable-not-default-storage-drivers/
-  - /rancher/v2.x/en/installation/resources/feature-flags/enable-not-default-storage-drivers/
 ---

 This feature allows you to use types for storage providers and provisioners that are not enabled by default.
@@ -1,7 +1,5 @@
 ---
 title: Rendering the Helm Template in an Air Gapped Environment
-shortTitle: Air Gap Upgrade
-weight: 1
 ---

 import Tabs from '@theme/Tabs';
@@ -1,7 +1,5 @@
 ---
 title: Installing Rancher on Azure Kubernetes Service
-shortTitle: AKS
-weight: 4
 ---

 This page covers how to install Rancher on Microsoft's Azure Kubernetes Service (AKS).
@@ -96,9 +94,9 @@ kubectl get service ingress-nginx-controller --namespace=ingress-nginx
 The result should look similar to the following:

 ```
-NAME                       TYPE           CLUSTER-IP     EXTERNAL-IP    PORT(S)                     
+NAME                       TYPE           CLUSTER-IP     EXTERNAL-IP    PORT(S)
 AGE
-ingress-nginx-controller   LoadBalancer   10.0.116.18    40.31.180.83   80:31229/TCP,443:31050/TCP  
+ingress-nginx-controller   LoadBalancer   10.0.116.18    40.31.180.83   80:31229/TCP,443:31050/TCP
 67s
 ```

@@ -1,9 +1,5 @@
 ---
 title: Installing Rancher on Amazon EKS
-shortTitle: Amazon EKS
-weight: 4
-aliases:
-  - /rancher/v2.x/en/installation/install-rancher-on-k8s/amazon-eks/
 ---

 This page covers two ways to install Rancher on EKS.
@@ -143,9 +139,9 @@ kubectl get service ingress-nginx-controller --namespace=ingress-nginx
 The result should look similar to the following:

 ```
-NAME                       TYPE           CLUSTER-IP     EXTERNAL-IP                                                              PORT(S)                     
+NAME                       TYPE           CLUSTER-IP     EXTERNAL-IP                                                              PORT(S)
 AGE
-ingress-nginx-controller   LoadBalancer   10.100.90.18   a904a952c73bf4f668a17c46ac7c56ab-962521486.us-west-2.elb.amazonaws.com   80:31229/TCP,443:31050/TCP  
+ingress-nginx-controller   LoadBalancer   10.100.90.18   a904a952c73bf4f668a17c46ac7c56ab-962521486.us-west-2.elb.amazonaws.com   80:31229/TCP,443:31050/TCP
 27m
 ```

@@ -1,7 +1,5 @@
 ---
 title: Installing Rancher on a Google Kubernetes Engine Cluster
-shortTitle: GKE
-weight: 5
 ---

 import Tabs from '@theme/Tabs';
@@ -1,14 +1,5 @@
 ---
 title: Rollbacks
-weight: 3
-aliases:
-  - /rancher/v2.x/en/upgrades/rollbacks
-  - /rancher/v2.x/en/installation/upgrades-rollbacks/rollbacks
-  - /rancher/v2.x/en/upgrades/ha-server-rollbacks
-  - /rancher/v2.x/en/upgrades/rollbacks/ha-server-rollbacks
-  - /rancher/v2.x/en/installation/upgrades-rollbacks/rollbacks/ha-server-rollbacks
-  - /rancher/v2.x/en/installation/install-rancher-on-k8s/upgrades-rollbacks/rollbacks
-  - /rancher/v2.x/en/installation/install-rancher-on-k8s/rollbacks/
 ---

 - [Rolling Back to Rancher v2.5.0+](#rolling-back-to-rancher-v2-5-0)
@@ -1,12 +1,5 @@
 ---
 title: Troubleshooting the Rancher Server Kubernetes Cluster
-weight: 276
-aliases:
-  - /rancher/v2.5/en/installation/k8s-install/helm-rancher/troubleshooting
-  - /rancher/v2.5/en/installation/ha/kubernetes-rke/troubleshooting
-  - /rancher/v2.5/en/installation/k8s-install/kubernetes-rke/troubleshooting
-  - /rancher/v2.5/en/installation/options/troubleshooting
-  - /rancher/v2.x/en/installation/resources/troubleshooting/
 ---

 This section describes how to troubleshoot an installation of Rancher on a Kubernetes cluster.
@@ -1,22 +1,7 @@
 ---
 title: Upgrades
-weight: 2
-aliases:
-  - /rancher/v2.5/en/upgrades/upgrades
-  - /rancher/v2.5/en/installation/upgrades-rollbacks/upgrades
-  - /rancher/v2.5/en/upgrades/upgrades/ha-server-upgrade-helm-airgap
-  - /rancher/v2.5/en/upgradeinstallation/install-rancher-on-k8s/upgrades/air-gap-upgrade/
-  - /rancher/v2.5/en/upgrades/upgrades/ha
-  - /rancher/v2.5/en/installation/install-rancher-on-k8s/upgrades/upgrades/ha
-  - /rancher/v2.5/en/installation/upgrades-rollbacks/upgrades/
-  - /rancher/v2.5/en/upgrades/upgrades/ha-server-upgrade-helm/
-  - /rancher/v2.5/en/installation/upgrades-rollbacks/upgrades/ha
-  - /rancher/v2.5/en/installation/install-rancher-on-k8s/upgrades-rollbacks/upgrades
-  - /rancher/v2.5/en/installation/install-rancher-on-k8s/upgrades-rollbacks/upgrades/ha
-  - /rancher/v2.5/en/installation/upgrades-rollbacks/
-  - /rancher/v2.5/en/upgrades/
-  - /rancher/v2.x/en/installation/install-rancher-on-k8s/upgrades/
 ---
+
 The following instructions will guide you through upgrading a Rancher server that was installed on a Kubernetes cluster with Helm. These steps also apply to air gap installs with Helm.

 For the instructions to upgrade Rancher installed on Kubernetes with RancherD, refer to [this page.](../other-installation-methods/install-rancher-on-linux/upgrade-rancherd.md)
@@ -1,6 +1,5 @@
 ---
 title: Installing Docker
-weight: 1
 ---

 Docker is required to be installed on nodes where the Rancher server will be installed with Helm or Docker.
@@ -1,9 +1,6 @@
 ---
 title: Port Requirements
 description: Read about port requirements needed in order for Rancher to operate properly, both for Rancher nodes and downstream Kubernetes cluster nodes
-weight: 300
-aliases:
-  - /rancher/v2.x/en/installation/requirements/ports/
 ---

 import Tabs from '@theme/Tabs';
@@ -1,6 +1,5 @@
 ---
 title: Docker Install Commands
-weight: 1
 ---

 The Docker installation is for Rancher users who want to test out Rancher.
@@ -1,9 +1,5 @@
 ---
 title: '1. Set up Infrastructure and Private Registry'
-weight: 100
-aliases:
-  - /rancher/v2.5/en/installation/air-gap-single-node/provision-host
-  - /rancher/v2.x/en/installation/other-installation-methods/air-gap/prepare-nodes/
 ---

 import Tabs from '@theme/Tabs';
@@ -1,9 +1,5 @@
 ---
 title: '3. Install Kubernetes (Skip for Docker Installs)'
-weight: 300
-aliases:
-  - /rancher/v2.5/en/installation/air-gap-high-availability/install-kube
-  - /rancher/v2.x/en/installation/other-installation-methods/air-gap/launch-kubernetes/
 ---

 import Tabs from '@theme/Tabs';
@@ -1,14 +1,5 @@
 ---
 title: 4. Install Rancher
-weight: 400
-aliases:
-  - /rancher/v2.5/en/installation/air-gap-high-availability/config-rancher-system-charts/
-  - /rancher/v2.5/en/installation/air-gap-high-availability/config-rancher-for-private-reg/
-  - /rancher/v2.5/en/installation/air-gap-single-node/install-rancher
-  - /rancher/v2.5/en/installation/air-gap/install-rancher
-  - /rancher/v2.5/en/installation/air-gap-installation/install-rancher/
-  - /rancher/v2.5/en/installation/air-gap-high-availability/install-rancher/
-  - /rancher/v2.x/en/installation/other-installation-methods/air-gap/install-rancher/
 ---

 import Tabs from '@theme/Tabs';
@@ -1,13 +1,5 @@
 ---
 title: '2. Collect and Publish Images to your Private Registry'
-weight: 200
-aliases:
-  - /rancher/v2.5/en/installation/air-gap-high-availability/prepare-private-registry/
-  - /rancher/v2.5/en/installation/air-gap-single-node/prepare-private-registry/
-  - /rancher/v2.5/en/installation/air-gap-single-node/config-rancher-for-private-reg/
-  - /rancher/v2.5/en/installation/air-gap-high-availability/config-rancher-for-private-reg/
-  - /rancher/v2.5/en/installation/air-gap-installation/prepare-private-reg/
-  - /rancher/v2.x/en/installation/other-installation-methods/air-gap/populate-private-registry/
 ---

 import Tabs from '@theme/Tabs';
@@ -1,9 +1,5 @@
 ---
 title: Rollbacks
-weight: 3
-aliases:
-  - /rancher/v2.5/en/installation/install-rancher-on-linux/rollbacks
-  - /rancher/v2.x/en/installation/install-rancher-on-linux/rollbacks/
 ---

 > **Note:** RancherD was an experimental feature available as part of Rancher v2.5.4 through v2.5.10 but is now deprecated and not available for recent releases.
@@ -1,9 +1,5 @@
 ---
 title: Upgrades
-weight: 2
-aliases:
-  - /rancher/v2.5/en/installation/install-rancher-on-linux/upgrades
-  - /rancher/v2.x/en/installation/install-rancher-on-linux/upgrades/
 ---

 > **Note:** RancherD was an experimental feature available as part of Rancher v2.5.4 through v2.5.10 but is now deprecated and not available for recent releases.
@@ -1,8 +1,5 @@
 ---
 title: '2. Install Kubernetes'
-weight: 200
-aliases:
-  - /rancher/v2.x/en/installation/other-installation-methods/behind-proxy/launch-kubernetes/
 ---

 Once the infrastructure is ready, you can continue with setting up an RKE cluster to install Rancher in.
@@ -1,8 +1,5 @@
 ---
 title: 3. Install Rancher
-weight: 300
-aliases:
-  - /rancher/v2.x/en/installation/other-installation-methods/behind-proxy/install-rancher/
 ---

 Now that you have a running RKE cluster, you can install Rancher in it. For security reasons all traffic to Rancher must be encrypted with TLS. For this tutorial you are going to automatically issue a self-signed certificate through [cert-manager](https://cert-manager.io/). In a real-world use-case you will likely use Let's Encrypt or provide your own certificate.
@@ -1,8 +1,5 @@
 ---
 title: '1. Set up Infrastructure'
-weight: 100
-aliases:
-  - /rancher/v2.x/en/installation/other-installation-methods/behind-proxy/prepare-nodes/
 ---

 In this section, you will provision the underlying infrastructure for your Rancher management server with internete access through a HTTP proxy.
@@ -1,9 +1,7 @@
 ---
 title: Certificate Troubleshooting
-weight: 4
-aliases:
-  - /rancher/v2.x/en/installation/other-installation-methods/single-node-docker/troubleshooting/
 ---
+
 ### How Do I Know if My Certificates are in PEM Format?

 You can recognize the PEM format by the following traits:
@@ -1,10 +1,5 @@
 ---
 title: Rolling Back Rancher Installed with Docker
-weight: 1015
-aliases:
-  - /rancher/v2.5/en/upgrades/single-node-rollbacks
-  - /rancher/v2.5/en/upgrades/rollbacks/single-node-rollbacks
-  - /rancher/v2.x/en/installation/other-installation-methods/single-node-docker/single-node-rollbacks/
 ---

 If a Rancher upgrade does not complete successfully, you'll have to roll back to your Rancher setup that you were using before [Docker Upgrade](upgrade-docker-installed-rancher.md). Rolling back restores:
@@ -1,13 +1,5 @@
 ---
 title: Upgrading Rancher Installed with Docker
-weight: 1010
-aliases:
-  - /rancher/v2.5/en/upgrades/single-node-upgrade/
-  - /rancher/v2.5/en/upgrades/upgrades/single-node-air-gap-upgrade
-  - /rancher/v2.5/en/upgrades/upgrades/single-node
-  - /rancher/v2.5/en/upgrades/upgrades/single-node-upgrade/
-  - /rancher/v2.5/en/installation/install-rancher-on-k8s/upgrades/upgrades/single-node/
-  - /rancher/v2.x/en/installation/other-installation-methods/single-node-docker/single-node-upgrades/
 ---

 import Tabs from '@theme/Tabs';
@@ -1,16 +1,12 @@
 ---
 title: Adding TLS Secrets
-weight: 2
-aliases:
-  - /rancher/v2.5/en/installation/resources/encryption/tls-secrets/
-  - /rancher/v2.x/en/installation/resources/tls-secrets/
 ---

 Kubernetes will create all the objects and services for Rancher, but it will not become available until we populate the `tls-rancher-ingress` secret in the `cattle-system` namespace with the certificate and key.

 Combine the server certificate followed by any intermediate certificate(s) needed into a file named `tls.crt`. Copy your certificate key into a file named `tls.key`.

-For example, [acme.sh](https://acme.sh) provides server certificate and CA chains in `fullchain.cer` file. 
+For example, [acme.sh](https://acme.sh) provides server certificate and CA chains in `fullchain.cer` file.
 This `fullchain.cer` should be renamed to `tls.crt` & certificate key file as `tls.key`.

 Use `kubectl` with the `tls` secret type to create the secrets.
@@ -1,9 +1,5 @@
 ---
 title: Choosing a Rancher Version
-weight: 1
-aliases:
-  - /rancher/v2.5/en/installation/options/server-tags
-  - /rancher/v2.x/en/installation/resources/choosing-version/
 ---

 import Tabs from '@theme/Tabs';
@@ -1,10 +1,5 @@
 ---
 title: About Custom CA Root Certificates
-weight: 1
-aliases:
-  - /rancher/v2.5/en/installation/options/custom-ca-root-certificate/
-  - /rancher/v2.5/en/installation/resources/choosing-version/encryption/custom-ca-root-certificate
-  - /rancher/v2.x/en/installation/resources/custom-ca-root-certificate/
 ---

 If you're using Rancher in an internal production environment where you aren't exposing apps publicly, use a certificate from a private certificate authority (CA).
@@ -1,12 +1,5 @@
 ---
 title: Helm Version Requirements
-weight: 3
-aliases:
-  - /rancher/v2.5/en/installation/options/helm-version
-  - /rancher/v2.5/en/installation/options/helm2
-  - /rancher/v2.5/en/installation/options/helm2/helm-init
-  - /rancher/v2.5/en/installation/options/helm2/helm-rancher
-  - /rancher/v2.x/en/installation/resources/helm-version/
 ---

 This section contains the requirements for Helm, which is the tool used to install Rancher on a high-availability Kubernetes cluster.
@@ -1,12 +1,5 @@
 ---
 title: Setting up Local System Charts for Air Gapped Installations
-weight: 120
-aliases:
-  - /rancher/v2.5/en/installation/air-gap-single-node/config-rancher-system-charts/_index.md
-  - /rancher/v2.5/en/installation/air-gap-high-availability/config-rancher-system-charts/_index.md
-  - /rancher/v2.5/en/installation/options/local-system-charts
-  - /rancher/v2.x/en/installation/resources/local-system-charts/
-  - /rancher/v2.x/en/installation/options/local-system-charts/
 ---

 The [System Charts](https://github.com/rancher/system-charts) repository contains all the catalog items required for features such as monitoring, logging, alerting and global DNS.
@@ -1,8 +1,5 @@
 ---
 title: Updating the Rancher Certificate
-weight: 10
-aliases:
-  - /rancher/v2.x/en/installation/resources/update-ca-cert/
 ---

 # Updating a Private CA Certificate
@@ -79,7 +76,7 @@ Also get the version string of the currently deployed Rancher chart:
 $ helm ls -A
 ```

-Upgrade the Helm application instance using the original configuration values and making sure to specify `ingress.tls.source=secret` as well as the current chart version to prevent an application upgrade.    
+Upgrade the Helm application instance using the original configuration values and making sure to specify `ingress.tls.source=secret` as well as the current chart version to prevent an application upgrade.

 If the certificate was signed by a private CA, add the `set privateCA=true` argument as well. Also make sure to read the documentation describing the initial installation using custom certificates.

@@ -219,7 +216,7 @@ Also get the version string of the currently deployed Rancher chart:
 $ helm ls -A
 ```

-Upgrade the Helm application instance using the original configuration values and making sure to specify the current chart version to prevent an application upgrade.    
+Upgrade the Helm application instance using the original configuration values and making sure to specify the current chart version to prevent an application upgrade.

 Also make sure to read the documentation describing the initial installation using custom certificates.

@@ -231,9 +228,9 @@ helm upgrade rancher rancher-stable/rancher \
  --set ...
 ```

-On upgrade, you can either 
+On upgrade, you can either

- remove `--set ingress.tls.source=secret \` from the Helm upgrade command, as shown above, or 
+- remove `--set ingress.tls.source=secret \` from the Helm upgrade command, as shown above, or

 - remove the `privateCA` parameter or set it to `false` because the CA is valid:

@@ -1,9 +1,5 @@
 ---
 title: Upgrading Cert-Manager with Helm 2
-weight: 2040
-aliases:
-  - /rancher/v2.5/en/installation/options/upgrading-cert-manager/helm-2-instructions
-  - /rancher/v2.5/en/installation/resources/choosing-version/encryption/upgrading-cert-manager/helm-2-instructions
 ---

 Rancher uses cert-manager to automatically generate and renew TLS certificates for HA deployments of Rancher. As of Fall 2019, three important changes to cert-manager are set to occur that you need to take action on if you have an HA deployment of Rancher:
@@ -1,11 +1,5 @@
 ---
 title: Upgrading Cert-Manager
-weight: 4
-aliases:
-  - /rancher/v2.5/en/installation/options/upgrading-cert-manager
-  - /rancher/v2.5/en/installation/options/upgrading-cert-manager/helm-2-instructions
-  - /rancher/v2.5/en/installation/resources/encryption/upgrading-cert-manager
-  - /rancher/v2.x/en/installation/resources/upgrading-cert-manager/
 ---

 Rancher uses cert-manager to automatically generate and renew TLS certificates for HA deployments of Rancher. As of Fall 2019, three important changes to cert-manager are set to occur that you need to take action on if you have an HA deployment of Rancher:
@@ -1,8 +1,5 @@
 ---
 title: Upgrading and Rolling Back Kubernetes
-weight: 70
-aliases:
-  - /rancher/v2.x/en/cluster-admin/upgrading-kubernetes/
 ---

 Following an upgrade to the latest version of Rancher, downstream Kubernetes clusters can be upgraded to use the latest supported version of Kubernetes.
@@ -1,8 +1,5 @@
 ---
 title: Upgrading Kubernetes without Upgrading Rancher
-weight: 1120
-aliases:
-  - /rancher/v2.x/en/admin-settings/k8s-metadata/
 ---

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

 Rancher's Kubernetes metadata contains information specific to the Kubernetes version that Rancher uses to provision [RKE clusters](../../pages-for-subheaders/launch-kubernetes-with-rancher.md). Rancher syncs the data periodically and creates custom resource definitions (CRDs) for **system images,** **service options** and **addon templates.** Consequently, when a new Kubernetes version is compatible with the Rancher server version, the Kubernetes metadata makes the new version available to Rancher for provisioning clusters. The metadata gives you an overview of the information that the [Rancher Kubernetes Engine](https://rancher.com/docs/rke/latest/en/) (RKE) uses for deploying various Kubernetes versions.

-This table below describes the CRDs that are affected by the periodic data sync. 
+This table below describes the CRDs that are affected by the periodic data sync.

 > **Note:** Only administrators can edit metadata CRDs. It is recommended not to update existing objects unless explicitly advised.

@@ -31,7 +28,7 @@ Administrators might configure the RKE metadata settings to do the following:

 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/advanced-user-guides/authentication-permissions-and-global-configuration/manage-role-based-access-control-rbac/global-permissions.md)

-To force Rancher to refresh the Kubernetes metadata, a manual refresh action is available under **Tools > Drivers > Refresh Kubernetes Metadata** on the right side corner. 
+To force Rancher to refresh the Kubernetes metadata, a manual refresh action is available under **Tools > Drivers > Refresh Kubernetes Metadata** on the right side corner.

 You can configure Rancher to only refresh metadata when desired by setting `refresh-interval-minutes` to `0` (see below) and using this button to perform the metadata refresh manually when desired.

@@ -1,9 +1,7 @@
 ---
 title: Overview
-weight: 1
-aliases:
-  - /rancher/v2.x/en/overview/
 ---
+
 Rancher is a container management platform built for organizations that deploy containers in production. Rancher makes it easy to run Kubernetes everywhere, meet IT requirements, and empower DevOps teams.

 # Run Kubernetes Everywhere
@@ -1,7 +1,6 @@
 ---
 title: Rancher AWS Quick Start Guide
 description: Read this step by step Rancher AWS guide to quickly deploy a Rancher server with a single-node downstream Kubernetes cluster attached.
-weight: 100
 ---
 The following steps will quickly deploy a Rancher server on AWS in a single-node K3s Kubernetes cluster, with a single-node downstream Kubernetes cluster attached.

@@ -1,7 +1,6 @@
 ---
 title: Rancher Azure Quick Start Guide
 description: Read this step by step Rancher Azure guide to quickly deploy a Rancher server with a single-node downstream Kubernetes cluster attached.
-weight: 100
 ---

 The following steps will quickly deploy a Rancher server on Azure in a single-node K3s Kubernetes cluster, with a single-node downstream Kubernetes cluster attached.
@@ -1,7 +1,6 @@
 ---
 title: Rancher DigitalOcean Quick Start Guide
 description: Read this step by step Rancher DigitalOcean guide to quickly deploy a Rancher server with a single-node downstream Kubernetes cluster attached.
-weight: 100
 ---
 The following steps will quickly deploy a Rancher server on DigitalOcean in a single-node K3s Kubernetes cluster, with a single-node downstream Kubernetes cluster attached.

@@ -1,7 +1,6 @@
 ---
 title: Rancher GCP Quick Start Guide
 description: Read this step by step Rancher GCP guide to quickly deploy a Rancher server with a single-node downstream Kubernetes cluster attached.
-weight: 100
 ---
 The following steps will quickly deploy a Rancher server on GCP in a single-node K3s Kubernetes cluster, with a single-node downstream Kubernetes cluster attached.

@@ -1,9 +1,7 @@
 ---
 title: Manual Quick Start
-weight: 300
-aliases:
-  - /rancher/v2.x/en/quick-start-guide/deployment/quickstart-manual-setup/
 ---
+
 Howdy Partner! This tutorial walks you through:

 - Installation of Rancher 2.x
@@ -1,9 +1,7 @@
 ---
 title: Vagrant Quick Start
-weight: 200
-aliases:
-  - /rancher/v2.x/en/quick-start-guide/deployment/quickstart-vagrant/
 ---
+
 The following steps quickly deploy a Rancher Server with a single node cluster attached.

 >**Note:** The intent of these guides is to quickly launch a sandbox that you can use to evaluate Rancher. These guides are not intended for production environments. For comprehensive setup instructions, see [Installation](../../../pages-for-subheaders/installation-and-upgrade.md).
@@ -1,8 +1,5 @@
 ---
 title: Workload with NodePort Quick Start
-weight: 200
-aliases:
-  - /rancher/v2.x/en/quick-start-guide/workload/quickstart-deploy-workload-nodeport/
 ---

 ### Prerequisite
@@ -1,8 +1,5 @@
 ---
 title: Workload with Ingress Quick Start
-weight: 100
-aliases:
-  - /rancher/v2.x/en/quick-start-guide/workload/quickstart-deploy-workload-ingress/
 ---

 ### Prerequisite