Reorganize doc structure

2026-09-24 20:18:18 +00:00 · 2020-08-28 14:50:55 -07:00
parent 9cdf2e0032
commit 8678b0ef28
210 changed files with 824 additions and 7248 deletions
@@ -1,6 +1,6 @@
 ---
 title: Authentication, Permissions and Global Configuration
-weight: 1100
+weight: 6
 aliases:
  - /rancher/v2.x/en/concepts/global-configuration/
  - /rancher/v2.x/en/tasks/global-configuration/
@@ -1,6 +1,6 @@
 ---
 title: API
-weight: 7500
+weight: 23
 ---

 ## How to use the API
@@ -1,6 +1,6 @@
 ---
 title: Backups and Disaster Recovery
-weight: 1000
+weight: 5
 ---

 This section is devoted to protecting your data in a disaster scenario.
@@ -1,5 +1,5 @@
 ---
-title: Backups
+title: Backup
 weight: 50
 aliases:
  - /rancher/v2.x/en/installation/after-installation/
@@ -0,0 +1,6 @@
+---
+title: Kubernetes Backups
+weight: 1
+---
+
+> This section is under construction.
@@ -1,9 +1,11 @@
 ---
 title: Backing up Rancher Installed on an RKE Kubernetes Cluster
+shortTitle: RKE Installs
 weight: 2
 aliases:
  - /rancher/v2.x/en/installation/after-installation/k8s-install-backup-and-restoration/
  - /rancher/v2.x/en/installation/backups-and-restoration/ha-backup-and-restoration/
+  - /rancher/v2.x/en/backups/backups/ha-backups
 ---
 This section describes how to create backups of your high-availability Rancher install.

@@ -1,6 +1,9 @@
 ---
 title: Backing up Rancher Installed on a K3s Kubernetes Cluster
+shortTitle: K3s Installs
 weight: 1
+aliases:
+  - /rancher/v2.x/en/backups/backups/k3s-backups
 ---

 When Rancher is installed on a high-availability Kubernetes cluster, we recommend using an external database to store the cluster data.
@@ -1,5 +1,6 @@
 ---
 title: Backing up Rancher Installed with Docker
+shortTitle: Docker Installs
 weight: 3
 aliases:
  - /rancher/v2.x/en/installation/after-installation/single-node-backup-and-restoration/
@@ -1,5 +1,5 @@
 ---
-title: Restorations
+title: Restore
 weight: 1010
 ---
 If you lose the data on your Rancher Server, you can restore it if you have backups stored in a safe location.
@@ -0,0 +1,4 @@
+---
+title: Kubernetes Installs
+weight: 1
+---
@@ -1,6 +1,9 @@
 ---
 title: Restoring Rancher Installed on a K3s Kubernetes Cluster
+shortTitle: K3s Installs
 weight: 1
+aliases:
+  - /rancher/v2.x/en/backups/restorations/k3s-restoration
 ---

 When Rancher is installed on a high-availability Kubernetes cluster, we recommend using an external database to store the cluster data.
@@ -1,9 +1,10 @@
 ---
 title: Restoring Backups—Kubernetes installs
-shortTitle: Kubernetes Installs
-weight: 370
+shortTitle: RKE Installs
+weight: 2
 aliases:
  - /rancher/v2.x/en/installation/after-installation/ha-backup-and-restoration/
+  - /rancher/v2.x/en/backups/restorations/ha-restoration
 ---

 This procedure describes how to use RKE to restore a snapshot of the Rancher Kubernetes cluster. 
@@ -1,7 +1,7 @@
 ---
 title: Restoring Backups—Docker Installs
 shortTitle: Docker Installs
-weight: 365
+weight: 3
 aliases:
  - /rancher/v2.x/en/installation/after-installation/single-node-backup-and-restoration/
 ---
@@ -1,6 +1,6 @@
 ---
 title: Best Practices Guide
-weight: 1000
+weight: 4
 ---

 The purpose of this section is to consolidate best practices for Rancher implementations. This also includes recommendations for related technologies, such as Kubernetes, Docker, containers, and more. The objective is to improve the outcome of a Rancher implementation using the operational experience of Rancher and its customers.
@@ -0,0 +1,119 @@
+---
+title: CIS Scans
+weight: 15
+---
+
+_Available as of v2.4.0_
+
+Rancher can run a security scan to check whether Kubernetes is deployed according to security best practices as defined in the CIS Kubernetes Benchmark.
+
+The Center for Internet Security (CIS) is a 501(c)(3) nonprofit organization, formed in October 2000, with a mission is to "identify, develop, validate, promote, and sustain best practice solutions for cyber defense and build and lead communities to enable an environment of trust in cyberspace". The organization is headquartered in East Greenbush, New York, with members including large corporations, government agencies, and academic institutions.
+
+CIS Benchmarks are best practices for the secure configuration of a target system. CIS Benchmarks are developed through the generous volunteer efforts of subject matter experts, technology vendors, public and private community members, and the CIS Benchmark Development team.
+
+The Benchmark provides recommendations of two types: Scored and Not Scored. We run tests related to only Scored recommendations.
+
+- [About the CIS Benchmark](#about-the-cis-benchmark)
+- [About the generated report](#about-the-generated-report)
+- [Test profiles](#test-profiles)
+- [Skipped and not applicable tests](#skipped-and-not-applicable-tests)
+  - [CIS Benchmark v1.4 skipped tests](#cis-benchmark-v1-4-skipped-tests)
+  - [CIS Benchmark v1.4 not applicable tests](#cis-benchmark-v1-4-not-applicable-tests)
+
+
+# About the CIS Benchmark
+
+The Center for Internet Security is a 501(c)(3) nonprofit organization, formed in October 2000, with a mission is to "identify, develop, validate, promote, and sustain best practice solutions for cyber defense and build and lead communities to enable an environment of trust in cyberspace". The organization is headquartered in East Greenbush, New York, with members including large corporations, government agencies, and academic institutions.
+
+CIS Benchmarks are best practices for the secure configuration of a target system. CIS Benchmarks are developed through the generous volunteer efforts of subject matter experts, technology vendors, public and private community members, and the CIS Benchmark Development team.
+
+The official Benchmark documents are available through the CIS website. The sign-up form to access the documents is [here.](https://learn.cisecurity.org/benchmarks)
+
+To check clusters for CIS Kubernetes Benchmark compliance, the security scan leverages [kube-bench,](https://github.com/aquasecurity/kube-bench) an open-source tool from Aqua Security.
+
+# About the Generated Report
+
+Each scan generates a report can be viewed in the Rancher UI and can be downloaded in CSV format.
+
+As of Rancher v2.4, the scan will use the CIS Benchmark v1.4. The Benchmark version is included in the generated report.
+
+The Benchmark provides recommendations of two types: Scored and Not Scored. Recommendations marked as Not Scored in the Benchmark are not included in the generated report.
+
+Some tests are designated as "Not Applicable." These tests will not be run on any CIS scan because of the way that Rancher provisions RKE clusters. For information on how test results can be audited, and why some tests are designated to be not applicable, refer to Rancher's [self-assessment guide for the corresponding Kubernetes version.]({{<baseurl>}}/rancher/v2.x/en/security/#the-cis-benchmark-and-self-assessment)
+
+The report contains the following information:
+
+| Column in Report | Description |
+|------------------|-------------|
+| ID               | The ID number of the CIS Benchmark. |
+| Description      | The description of the CIS Benchmark test. |
+| Remediation      | What needs to be fixed in order to pass the test. |
+| State of Test    | Indicates if the test passed, failed, was skipped, or was not applicable. |
+| Node type        | The node role, which affects which tests are run on the node. Master tests are run on controlplane nodes, etcd tests are run on etcd nodes, and node tests are run on the worker nodes. |
+| Nodes            | The name(s) of the node that the test was run on. |
+| Passed_Nodes | The name(s) of the nodes that the test passed on. |
+| Failed_Nodes | The name(s) of the nodes that the test failed on. |
+
+Refer to [the table in the cluster hardening guide]({{<baseurl>}}/rancher/v2.x/en/security/#rancher-hardening-guide) for information on which versions of Kubernetes, the Benchmark, Rancher, and our cluster hardening guide correspond to each other. Also refer to the hardening guide for configuration files of CIS-compliant clusters and information on remediating failed tests.
+
+
+
+# Test Profiles
+
+For every CIS benchmark version, Rancher ships with two types of profiles. These profiles are named based on the type of cluster (e.g. `RKE`), the CIS benchmark version (e.g. CIS 1.4) and the profile type (e.g. `Permissive` or `Hardened`). For example, a full profile name would be `RKE-CIS-1.4-Permissive`
+
+All profiles will have a set of not applicable tests that will be skipped during the CIS scan. These tests are not applicable based on how a RKE cluster manages Kubernetes.
+
+There are 2 types of profiles:
+
+- **Permissive:** This profile has a set of tests that have been will be skipped as these tests will fail on a default RKE Kubernetes cluster. Besides the list of skipped tests, the profile will also not run the not applicable tests.
+- **Hardened:** This profile will not skip any tests, except for the non-applicable tests.
+
+In order to pass the "Hardened" profile, you will need to follow the steps on the [hardening guide]({{<baseurl>}}/rancher/v2.x/en/security/#rancher-hardening-guide) and use the `cluster.yml` defined in the hardening guide to provision a hardened cluster.
+
+# Skipped and Not Applicable Tests
+
+### CIS Benchmark v1.4 Skipped Tests
+
+Number | Description | Reason for Skipping
+---|---|---
+1.1.11 | "Ensure that the admission control plugin AlwaysPullImages is set (Scored)" | Enabling AlwaysPullImages can use significant bandwidth.
+1.1.21 | "Ensure that the --kubelet-certificate-authority argument is set as appropriate (Scored)" | When generating serving certificates, functionality could break in conjunction with hostname overrides which are required for certain cloud providers.
+1.1.24 | "Ensure that the admission control plugin PodSecurityPolicy is set (Scored)" | Enabling Pod Security Policy can cause applications to unexpectedly fail.
+1.1.34 | "Ensure that the --encryption-provider-config argument is set as appropriate (Scored)" | Enabling encryption changes how data can be recovered as data is encrypted.
+1.1.35 | "Ensure that the encryption provider is set to aescbc (Scored)" | Enabling encryption changes how data can be recovered as data is encrypted.
+1.1.36 | "Ensure that the admission control plugin EventRateLimit is set (Scored)" | EventRateLimit needs to be tuned depending on the cluster.
+1.2.2 | "Ensure that the --address argument is set to 127.0.0.1 (Scored)" | Adding this argument prevents Rancher's monitoring tool to collect metrics on the scheduler.
+1.3.7 | "Ensure that the --address argument is set to 127.0.0.1 (Scored)" | Adding this argument prevents Rancher's monitoring tool to collect metrics on the controller manager.
+1.4.12 | "Ensure that the etcd data directory ownership is set to etcd:etcd (Scored)" | A system service account is required for etcd data directory ownership. Refer to Rancher's hardening guide for more details on how to configure this ownership.
+1.7.2 | "Do not admit containers wishing to share the host process ID namespace (Scored)" | Enabling Pod Security Policy can cause applications to unexpectedly fail.
+1.7.3 | "Do not admit containers wishing to share the host IPC namespace (Scored)" | Enabling Pod Security Policy can cause applications to unexpectedly fail.
+1.7.4 | "Do not admit containers wishing to share the host network namespace (Scored)" | Enabling Pod Security Policy can cause applications to unexpectedly fail.
+1.7.5 | " Do not admit containers with allowPrivilegeEscalation (Scored)" | Enabling Pod Security Policy can cause applications to unexpectedly fail.
+2.1.6 | "Ensure that the --protect-kernel-defaults argument is set to true (Scored)" | System level configurations are required prior to provisioning the cluster in order for this argument to be set to true.
+2.1.10 | "Ensure that the --tls-cert-file and --tls-private-key-file arguments are set as appropriate (Scored)" | When generating serving certificates, functionality could break in conjunction with hostname overrides which are required for certain cloud providers.
+
+### CIS Benchmark v1.4 Not Applicable Tests
+
+Number | Description | Reason for being not applicable
+---|---|---
+1.1.9 | "Ensure that the --repair-malformed-updates argument is set to false (Scored)" | The argument --repair-malformed-updates has been removed as of Kubernetes version 1.14
+1.3.6 | "Ensure that the RotateKubeletServerCertificate argument is set to true" | Cluster provisioned by RKE handles certificate rotation directly through RKE.
+1.4.1 | "Ensure that the API server pod specification file permissions are set to 644 or more restrictive (Scored)" | Cluster provisioned by RKE doesn't require or maintain a configuration file for kube-apiserver.
+1.4.2 | "Ensure that the API server pod specification file ownership is set to root:root (Scored)" | Cluster provisioned by RKE doesn't require or maintain a configuration file for kube-apiserver.
+1.4.3 | "Ensure that the controller manager pod specification file permissions are set to 644 or more restrictive (Scored)" | Cluster provisioned by RKE doesn't require or maintain a configuration file for controller-manager.
+1.4.4 | "Ensure that the controller manager pod specification file ownership is set to root:root (Scored)" | Cluster provisioned by RKE doesn't require or maintain a configuration file for controller-manager.
+1.4.5 | "Ensure that the scheduler pod specification file permissions are set to 644 or more restrictive (Scored)" | Cluster provisioned by RKE doesn't require or maintain a configuration file for scheduler.
+1.4.6 | "Ensure that the scheduler pod specification file ownership is set to root:root (Scored)" | Cluster provisioned by RKE doesn't require or maintain a configuration file for scheduler.
+1.4.7 | "Ensure that the etcd pod specification file permissions are set to 644 or more restrictive (Scored)" | Cluster provisioned by RKE doesn't require or maintain a configuration file for etcd.
+1.4.8 | "Ensure that the etcd pod specification file ownership is set to root:root (Scored)" | Cluster provisioned by RKE doesn't require or maintain a configuration file for etcd.
+1.4.13 |  "Ensure that the admin.conf file permissions are set to 644 or more restrictive (Scored)" | Cluster provisioned by RKE does not store the kubernetes default kubeconfig credentials file on the nodes.
+1.4.14 | "Ensure that the admin.conf file ownership is set to root:root (Scored)" | Cluster provisioned by RKE does not store the kubernetes default kubeconfig credentials file on the nodes.
+2.1.8 | "Ensure that the --hostname-override argument is not set (Scored)" | Clusters provisioned by RKE clusters and most cloud providers require hostnames.
+2.1.12 | "Ensure that the --rotate-certificates argument is not set to false (Scored)" | Cluster provisioned by RKE handles certificate rotation directly through RKE.
+2.1.13 | "Ensure that the RotateKubeletServerCertificate argument is set to true (Scored)" | Cluster provisioned by RKE handles certificate rotation directly through RKE.
+2.2.3 | "Ensure that the kubelet service file permissions are set to 644 or more restrictive (Scored)" | Cluster provisioned by RKE doesn’t require or maintain a configuration file for the kubelet service.
+2.2.4 | "Ensure that the kubelet service file ownership is set to root:root (Scored)" | Cluster provisioned by RKE doesn’t require or maintain a configuration file for the kubelet service.
+2.2.9 | "Ensure that the kubelet configuration file ownership is set to root:root (Scored)" | RKE doesn’t require or maintain a configuration file for the kubelet.
+2.2.10 | "Ensure that the kubelet configuration file has permissions set to 644 or more restrictive (Scored)" | RKE doesn’t require or maintain a configuration file for the kubelet.
+
@@ -0,0 +1,147 @@
+---
+title: Legacy UI Documentation
+weight: 1
+---
+_Available as of v2.4.0_
+
+- [Prerequisites](#prerequisites)
+- [Running a scan](#running-a-scan)
+- [Scheduling recurring scans](#scheduling-recurring-scans)
+- [Skipping tests](#skipping-tests)
+- [Setting alerts](#setting-alerts)
+- [Deleting a report](#deleting-a-report)
+- [Downloading a report](#downloading-a-report)
+
+
+# Prerequisites
+
+To run security scans on a cluster and access the generated reports, you must be an [Administrator]({{<baseurl>}}/rancher/v2.x/en/admin-settings/rbac/global-permissions/) or [Cluster Owner.]({{<baseurl>}}/rancher/v2.x/en/admin-settings/rbac/cluster-project-roles/)
+
+Rancher can only run security scans on clusters that were created with RKE, which includes custom clusters and clusters that Rancher created in an infrastructure provider such as Amazon EC2 or GCE. Imported clusters and clusters in hosted Kubernetes providers can't be scanned by Rancher.
+
+The security scan cannot run in a cluster that has Windows nodes.
+
+You will only be able to see the CIS scan reports for clusters that you have access to.
+
+# Running a Scan
+
+1. From the cluster view in Rancher, click **Tools > CIS Scans.**
+1. Click **Run Scan.**
+1. Choose a CIS scan profile.
+
+**Result:** A report is generated and displayed in the **CIS Scans** page. To see details of the report, click the report's name.
+
+# Scheduling Recurring Scans
+
+Recurring scans can be scheduled to run on any RKE Kubernetes cluster.
+
+To enable recurring scans, edit the advanced options in the cluster configuration during cluster creation or after the cluster has been created.
+
+To schedule scans for an existing cluster:
+
+1. Go to the cluster view in Rancher.
+1. Click **Tools > CIS Scans.**
+1. Click **Add Schedule.** This takes you to the section of the cluster editing page that is applicable to configuring a schedule for CIS scans. (This section can also be reached by going to the cluster view, clicking **&#8942; > Edit,** and going to the **Advanced Options.**)
+1. In the **CIS Scan Enabled** field, click **Yes.**
+1. In the **CIS Scan Profile** field, choose a **Permissive** or **Hardened** profile. The corresponding CIS Benchmark version is included in the profile name. Note: Any skipped tests [defined in a separate ConfigMap](#skipping-tests) will be skipped regardless of whether a **Permissive** or **Hardened** profile is selected. When selecting the the permissive profile, you should see which tests were skipped by Rancher (tests that are skipped by default for RKE clusters) and which tests were skipped by a Rancher user. In the hardened test profile, the only skipped tests will be skipped by users.
+1. In the **CIS Scan Interval (cron)** job, enter a [cron expression](https://en.wikipedia.org/wiki/Cron#CRON_expression) to define how often the cluster will be scanned.
+1. In the **CIS Scan Report Retention** field, enter the number of past reports that should be kept.
+
+**Result:** The security scan will run and generate reports at the scheduled intervals.
+
+The test schedule can be configured in the `cluster.yml`:
+
+```yaml
+scheduled_cluster_scan:
+    enabled: true
+    scan_config:
+        cis_scan_config:
+            override_benchmark_version: rke-cis-1.4
+            profile: permissive
+    schedule_config:
+        cron_schedule: 0 0 * * *
+        retention: 24
+```
+
+
+# Skipping Tests
+
+You can define a set of tests that will be skipped by the CIS scan when the next report is generated.
+
+These tests will be skipped for subsequent CIS scans, including both manually triggered and scheduled scans, and the tests will be skipped with any profile.
+
+The skipped tests will be listed alongside the test profile name in the cluster configuration options when a test profile is selected for a recurring cluster scan. The skipped tests will also be shown every time a scan is triggered manually from the Rancher UI by clicking **Run Scan.** The display of skipped tests allows you to know ahead of time which tests will be run in each scan.
+
+To skip tests, you will need to define them in a Kubernetes ConfigMap resource. Each skipped CIS scan test is listed in the ConfigMap alongside the version of the CIS benchmark that the test belongs to.
+
+To skip tests by editing a ConfigMap resource,
+
+1. Create a `security-scan` namespace.
+1. Create a ConfigMap named `security-scan-cfg`.
+1. Enter the skip information under the key `config.json` in the following format:
+
+    ```json
+    {
+      "skip": {
+        "rke-cis-1.4": [ 
+          "1.1.1", 
+          "1.2.2"
+        ]
+      }
+    }
+    ```
+    
+    In the example above, the CIS benchmark version is specified alongside the tests to be skipped for that version.
+
+**Result:** These tests will be skipped on subsequent scans that use the defined CIS Benchmark version.
+
+# Setting Alerts
+
+Rancher provides a set of alerts for cluster scans. which are not configured to have notifiers by default:
+
+- A manual cluster scan was completed
+- A manual cluster scan has failures
+- A scheduled cluster scan was completed
+- A scheduled cluster scan has failures
+
+> **Prerequisite:** You need to configure a [notifier]({{<baseurl>}}/rancher/v2.x/en/cluster-admin/tools/notifiers/) before configuring, sending, or receiving alerts.
+
+To activate an existing alert for a CIS scan result,
+
+1. From the cluster view in Rancher, click **Tools > Alerts.**
+1. Go to the section called **A set of alerts for cluster scans.**
+1. Go to the alert you want to activate and click **&#8942; > Activate.**
+1. Go to the alert rule group **A set of alerts for cluster scans** and click **&#8942; > Edit.**
+1. Scroll down to the **Alert** section. In the **To** field, select the notifier that you would like to use for sending alert notifications.
+1. Optional: To limit the frequency of the notifications, click on **Show advanced options** and configure the time interval of the alerts.
+1. Click **Save.**
+
+**Result:** The notifications will be triggered when the a scan is run on a cluster and the active alerts have satisfied conditions.
+
+To create a new alert,
+
+1. Go to the cluster view and click **Tools > CIS Scans.**
+1. Click **Add Alert.**
+1. Fill out the form. 
+1. Enter a name for the alert.
+1. In the **Is** field, set the alert to be triggered when a scan is completed or when a scan has a failure.
+1. In the **Send a** field, set the alert as a **Critical,** **Warning,** or **Info** alert level.
+1. Choose a [notifier]({{<baseurl>}}/rancher/v2.x/en/cluster-admin/tools/notifiers/) for the alert.
+
+**Result:** The alert is created and activated. The notifications will be triggered when the a scan is run on a cluster and the active alerts have satisfied conditions.
+
+For more information about alerts, refer to [this page.]({{<baseurl>}}/rancher/v2.x/en/cluster-admin/tools/alerts/)
+
+# Deleting a Report
+
+1. From the cluster view in Rancher, click **Tools > CIS Scans.**
+1. Go to the report that should be deleted.
+1. Click the **&#8942; > Delete.**
+1. Click **Delete.**
+
+# Downloading a Report
+
+1. From the cluster view in Rancher, click **Tools > CIS Scans.**
+1. Go to the report that you want to download. Click **&#8942; > Download.**
+
+**Result:** The report is downloaded in CSV format. For more information on each columns, refer to the [section about the generated report.](#about-the-generated-report)
@@ -3,7 +3,7 @@ title: Using the Rancher Command Line Interface
 description: The Rancher CLI is a unified tool that you can use to interact with Rancher. With it, you can operate Rancher using a command line interface rather than the GUI
 metaTitle: "Using the Rancher Command Line Interface "
 metaDescription: "The Rancher CLI is a unified tool that you can use to interact with Rancher. With it, you can operate Rancher using a command line interface rather than the GUI"
-weight: 6000
+weight: 20
 ---

 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.
@@ -1,6 +1,6 @@
 ---
 title: Cluster Administration
-weight: 2005
+weight: 8
 ---

 After you provision a cluster in Rancher, you can begin using powerful Kubernetes features to deploy and scale your containerized applications in development, testing, or production environments.
@@ -0,0 +1,8 @@
+---
+title: Cluster Explorer
+weight: 10
+---
+
+_Available as of v2.5_
+
+The cluster explorer is a new feature in Rancher v2.5 that allows you to view and manipulate all of the custom resources and CRDs in a Kubernetes cluster from the Rancher UI.
@@ -1,7 +1,7 @@
 ---
 title: Setting up Kubernetes Clusters in Rancher
 description: Provisioning Kubernetes Clusters
-weight: 2000
+weight: 7
 aliases:
  - /rancher/v2.x/en/concepts/clusters/
  - /rancher/v2.x/en/concepts/clusters/cluster-providers/
@@ -44,6 +44,12 @@ The figure below illustrates the high-level architecture of Rancher 2.x. The fig

 Use Rancher to set up and configure your Kubernetes cluster.

+The form to create EKS clusters was improved in Rancher 2.5.
+
+{{% tabs %}}
+{{% tab "Rancher v2.5+" %}}
+{{% /tab %}}
+{{% tab "Rancher prior to v2.5" %}}
 1. From the **Clusters** page, click **Add Cluster**.

 1. Choose **Amazon EKS**.
@@ -134,6 +140,8 @@ If you chose this option, you must also choose a **VPC & Subnet** that allow you
 1. Click **Create**.

 {{< result_create-cluster >}}
+{{% /tab %}}
+{{% /tabs %}}

 ## Troubleshooting

@@ -0,0 +1,12 @@
+---
+title: Registering Clusters
+weight: 6
+---
+
+> This section is under construction.
+
+The following types of Kubernetes clusters can be registered in Rancher:
+
+- K3s
+- RancherD
+- EKS
@@ -1,4 +0,0 @@
---
-title: Registering K3s, Rancher or EKS Clusters
-weight: 6
---
@@ -1,6 +1,6 @@
 ---
 title: Contributing to Rancher
-weight: 9000
+weight: 26
 aliases:
  - /rancher/v2.x/en/faq/contributing/
 ---
@@ -1,4 +0,0 @@
---
-title: Dashboard
-weight: 5000
---
@@ -1,4 +0,0 @@
---
-title: Backup and Restore
-weight: 7
---
@@ -1,4 +0,0 @@
---
-title: CIS Security Scans
-weight: 6
---
@@ -1,4 +0,0 @@
---
-title: Cluster Explorer
-weight: 1
---
@@ -1,4 +0,0 @@
---
-title: OPA
-weight: 5
---
@@ -1,4 +0,0 @@
---
-title: Repos
-weight: 8
---
@@ -0,0 +1,16 @@
+---
+title: Deploying Applications across Clusters
+weight: 18
+---
+
+> This section is under construction.
+
+### Fleet
+
+_Available in v2.5_
+
+Refer to the [Fleet documentation.]()
+
+### Legacy UI Documentation for Multi-cluster Apps
+
+Refer to the documentation [here.]()
@@ -0,0 +1,8 @@
+---
+title: Fleet
+weight: 1
+---
+
+_Available as of Rancher v2.5_
+
+This section is under construction.
@@ -1,7 +1,8 @@
 ---
-title: Multi-Cluster Apps
-weight: 600
+title: Legacy UI Documentation
+weight: 2
 ---
+
 _Available as of v2.2.0_

 Typically, most applications are deployed on a single Kubernetes cluster, but there will be times you might want to deploy multiple copies of the same application across different clusters and/or projects. In Rancher, a _multi-cluster application_,  is an application deployed using a Helm chart across multiple clusters. With the ability to deploy the same application across multiple clusters, it avoids the repetition of the same action on each cluster, which could introduce user error during application configuration. With multi-cluster applications, you can customize to have the same configuration across all projects/clusters as well as have the ability to change the configuration based on your target project. Since multi-cluster application is considered a single application, it's easy to manage and maintain this application.
@@ -1,6 +1,6 @@
 ---
 title: FAQ
-weight: 8000
+weight: 24
 aliases:
  - /rancher/v2.x/en/about/
 ---
@@ -0,0 +1,6 @@
+---
+title: Helm Charts in Rancher
+weight: 17
+---
+
+> This section is under construction.
@@ -0,0 +1,10 @@
+---
+title: Apps and Marketplace
+weight: 1
+---
+
+_Available as of v2.5_
+
+> This section is under construction.
+
+In this section, you'll learn how to manage Helm chart repositories and applications in Rancher.
@@ -1,11 +1,12 @@
 ---
-title: Catalogs, Helm Charts and Apps
+title: Legacy UI Documentation
 description: Rancher enables the use of catalogs to repeatedly deploy applications easily. Catalogs are GitHub or Helm Chart repositories filled with deployment-ready apps.
 weight: 4000
 aliases:
  - /rancher/v2.x/en/concepts/global-configuration/catalog/
  - /rancher/v2.x/en/concepts/catalogs/
  - /rancher/v2.x/en/tasks/global-configuration/catalog/
+  - /rancher/v2.x/en/catalog
 ---

 Rancher provides the ability to use a catalog of Helm charts that make it easy to repeatedly deploy applications.
@@ -4,6 +4,7 @@ weight: 200
 aliases:
  - /rancher/v2.x/en/tasks/global-configuration/catalog/adding-custom-catalogs/
  - /rancher/v2.x/en/catalog/custom/adding
+  - /rancher/v2.x/en/catalog/adding-catalogs
 ---

 Custom catalogs can be added into Rancher at a global scope, cluster scope, or project scope.
@@ -3,6 +3,7 @@ title: Enabling and Disabling Built-in Global Catalogs
 weight: 100
 aliases:
  - /rancher/v2.x/en/tasks/global-configuration/catalog/enabling-default-catalogs/
+  - /rancher/v2.x/en/catalog/built-in
 ---

 There are default global catalogs packaged as part of Rancher.
@@ -3,6 +3,7 @@ title: Custom Catalog Configuration Reference
 weight: 300
 aliases:
  - /rancher/v2.x/en/catalog/catalog-config
+  - /rancher/v2.x/en/catalog/catalog-config
 ---

 Any user can create custom catalogs to add into Rancher. Besides the content of the catalog, users must ensure their catalogs are able to be added into Rancher.
@@ -4,6 +4,7 @@ weight: 400
 aliases:
  - /rancher/v2.x/en/tasks/global-configuration/catalog/customizing-charts/
  - /rancher/v2.x/en/catalog/custom/creating
+  - /rancher/v2.x/en/catalog/creating-apps
 ---

 Rancher's catalog service requires any custom catalogs to be structured in a specific format for the catalog service to be able to leverage it in Rancher.
@@ -1,6 +1,8 @@
 ---
 title: Global DNS
 weight: 5010
+aliases:
+  - /rancher/v2.x/en/catalog/globaldns
 ---

 _Available as of v2.2.0_
@@ -1,6 +1,8 @@
 ---
 title: Managing Catalog Apps
 weight: 500
+aliases:
+  - /rancher/v2.x/en/catalog/managing-apps
 ---

 After deploying an application, one of the benefits of using an application versus individual workloads/resources is the ease of being able to manage many workloads/resources applications. Apps can be cloned, upgraded or rolled back.
@@ -0,0 +1,9 @@
+---
+title: Multi-Cluster Apps
+weight: 600
+aliases:
+  - /rancher/v2.x/en/catalog/multi-cluster-apps
+---
+_Available as of v2.2.0_
+
+The documentation about multi-cluster apps has moved [here.]({{<baseurl>}}/rancher/v2.x/en/deploy-across-clusters/multi-cluster-apps)
@@ -1,6 +1,8 @@
 ---
 title: "Tutorial: Example Custom Chart Creation"
 weight: 800
+aliases:
+  - /rancher/v2.x/en/catalog/tutorial
 ---

 In this tutorial, you'll learn how to create a Helm chart and deploy it to a  repository. The repository can then be used as a source for a custom catalog in Rancher.
@@ -1,7 +1,7 @@
 ---
-title: Installing Rancher
+title: Installing/Upgrading Rancher
 description: Learn how to install Rancher in development and production environments. Read about single node and high availability installation
-weight: 50
+weight: 3
 aliases:
  - /rancher/v2.x/en/installation/how-ha-works/
 ---
@@ -0,0 +1,17 @@
+---
+title: Install Rancher on a Kubernetes Cluster
+description: Learn how to install Rancher in development and production environments. Read about single node and high availability installation
+weight: 3
+---
+
+Rancher is both a platform and a Kubernetes distribution. In this section you'll learn how to install Rancher as a Helm chart on an existing Kubernetes cluster, without installing the Rancher Kubernetes distribution.
+
+There are two main ways that Rancher can be installed:
+
+1. You can use Helm to install the Rancher Helm chart on any Kubernetes cluster.
+2. You can use the Rancher CLI to install a Rancher Kubernetes cluster. This cluster comes with the Rancher Helm chart built in.
+
+The installation path that you choose will affect the way that you upgrade Rancher, but not the way that Rancher is backed up and restored.
+
+This section focuses on the installation path in which the Rancher CLI is used to provision a new Kubernetes cluster with the Rancher Helm chart built in.
+
@@ -1,11 +1,15 @@
 ---
-title: 3. Install Rancher on the Kubernetes Cluster
-description: Rancher installation is managed using the Helm Kubernetes package manager. Use Helm to install the prerequisites and charts to install Rancher
-weight: 200
-aliases:
-  - /rancher/v2.x/en/installation/ha/helm-rancher
+title: Install
+weight: 1
 ---

+> **Prerequisite:**
+> Set up the Rancher Kubernetes cluster. Rancher can be installed on any Kubernetes cluster.
+>
+> This cluster can use upstream Kubernetes, or it can use one of Rancher's Kubernetes distributions, or it can be a managed Kubernetes cluster from a provider such as Amazon EKS.
+
+# Install the Rancher Helm Chart
+
 Rancher is installed using the Helm package manager for Kubernetes. Helm charts provide templating syntax for Kubernetes YAML manifest documents.

 With Helm, we can create configurable deployments instead of just using static files. For more information about creating your own catalog of deployments, check out the docs at https://helm.sh/.
@@ -263,3 +267,8 @@ That's it. You should have a functional Rancher server.
 In a web browser, go to the DNS name that forwards traffic to your load balancer. Then you should be greeted by the colorful login page.

 Doesn't work? Take a look at the [Troubleshooting]({{<baseurl>}}/rancher/v2.x/en/installation/options/troubleshooting/) Page
+
+
+### Optional Next Steps
+
+Enable the Enterprise Cluster Manager.
@@ -0,0 +1,7 @@
+---
+title: Installing Rancher on an AKS Kubernetes Cluster
+shortTitle: AKS
+weight: 2
+---
+
+> This section is under construction.
@@ -0,0 +1,7 @@
+---
+title: Installing Rancher on Any Kubernetes Cluster
+shortTitle: Any Kubernetes Cluster
+weight: 4
+---
+
+> This section is under construction.
@@ -0,0 +1,7 @@
+---
+title: Installing Rancher on an EKS Kubernetes Cluster
+shortTitle: EKS
+weight: 1
+---
+
+> This section is under construction.
@@ -0,0 +1,7 @@
+---
+title: Installing Rancher on a GKE Kubernetes Cluster
+shortTitle: GKE
+weight: 3
+---
+
+> This section is under construction.
@@ -1,18 +1,17 @@
 ---
 title: Upgrades and Rollbacks
 weight: 150
+aliases:
+  - /rancher/v2.x/en/upgrades
 ---

 ### Upgrading Rancher

- [Upgrades]({{<baseurl>}}/rancher/v2.x/en/upgrades/upgrades/)
+To upgrade Rancher, refer to [these instructions.]({{<baseurl>}}/rancher/v2.x/en/installation/install-rancher-on-k8s/upgrades/upgrades/)

 ### Rolling Back Unsuccessful Upgrades

-In the event that your Rancher Server does not upgrade successfully, you can rollback to your installation prior to upgrade:
-
- [Rollbacks for Rancher installed with Docker]({{<baseurl>}}/rancher/v2.x/en/upgrades/single-node-rollbacks)
- [Rollbacks for Rancher installed on a Kubernetes cluster]({{<baseurl>}}/rancher/v2.x/en/upgrades/ha-server-rollbacks)
+In the event that your Rancher Server does not upgrade successfully, you can rollback to your installation prior to upgrade using these instructions: [Rollbacks for Rancher installed on a Kubernetes cluster]({{<baseurl>}}/rancher/v2.x/en/upgrades/ha-server-rollbacks)

 > **Note:** If you are rolling back to versions in either of these scenarios, you must follow some extra [instructions]({{<baseurl>}}/rancher/v2.x/en/upgrades/rollbacks/) in order to get your clusters working.
 >
@@ -1,9 +1,21 @@
 ---
 title: Rollbacks
 weight: 1010
+aliases:
+  - /rancher/v2.x/en/upgrades/rollbacks
 ---
+
+
+> This page is under construction.
+
 This section contains information about how to rollback your Rancher server to a previous version.

+If you upgrade Rancher and the upgrade does not complete successfully, you may need to [restore Rancher from backup.](../../backups/restores)
+
+Restoring a snapshot of the Rancher Server cluster will revert Rancher to the version and state at the time of the snapshot.
+
+>**Note:** Managed clusters are authoritative for their state. This means restoring the rancher server will not revert workload deployments or changes made on managed clusters after the snapshot was taken.
+
 - [Rolling back Rancher installed with Docker]({{<baseurl>}}/rancher/v2.x/en/upgrades/rollbacks/single-node-rollbacks/)
 - [Rolling back Rancher installed on a Kubernetes cluster]({{<baseurl>}}/rancher/v2.x/en/upgrades/rollbacks/ha-server-rollbacks/)

@@ -14,7 +26,6 @@ If you are rolling back to versions in either of these scenarios, you must follo
 - Rolling back from v2.1.6+ to any version between v2.1.0 - v2.1.5 or v2.0.0 - v2.0.10.
 - Rolling back from v2.0.11+ to any version between v2.0.0 - v2.0.10.  

-
 Because of the changes necessary to address [CVE-2018-20321](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20321), special steps are necessary if the user wants to roll back to a previous version of Rancher where this vulnerability exists. The steps are as follows:

 1. Record the `serviceAccountToken` for each cluster.  To do this, save the following script on a machine with `kubectl` access to the Rancher management plane and execute it.  You will need to run these commands on the machine where the rancher container is running. Ensure JQ is installed before running the command. The commands will vary depending on how you installed Rancher.
@@ -3,6 +3,7 @@ title: Kubernetes Rollback
 weight: 1025
 aliases:
  - /rancher/v2.x/en/upgrades/ha-server-rollbacks
+  - /rancher/v2.x/en/upgrades/rollbacks/ha-server-rollbacks
 ---

 If you upgrade Rancher and the upgrade does not complete successfully, you may need to rollback your Rancher Server to its last healthy state.
@@ -1,11 +1,13 @@
 ---
 title: Upgrades
 weight: 1005
+aliases:
+  - /rancher/v2.x/en/upgrades/upgrades
 ---
 This section contains information about how to upgrade your Rancher server to a newer version. Regardless if you installed in an air gap environment or not, the upgrade steps mainly depend on whether you have a single node or high-availability installation of Rancher. Select from the following options:

- [Upgrading Rancher installed with Docker]({{<baseurl>}}/rancher/v2.x/en/upgrades/upgrades/single-node/)
- [Upgrading Rancher installed on a Kubernetes cluster]({{<baseurl>}}/rancher/v2.x/en/upgrades/upgrades/ha/)
+- [Upgrading Rancher installed with Docker]({{<baseurl>}}/rancher/v2.x/en/installation/install-rancher-on-k8s/upgrades/upgrades/single-node/)
+- [Upgrading Rancher installed on a Kubernetes cluster]({{<baseurl>}}/rancher/v2.x/en/installation/install-rancher-on-k8s/upgrades/upgrades/ha/)

 ### Known Upgrade Issues

@@ -4,6 +4,7 @@ weight: 1030
 aliases:
  - /rancher/v2.x/en/upgrades/ha-server-upgrade/
  - /rancher/v2.x/en/upgrades/upgrades/ha-server-upgrade/
+  - /rancher/v2.x/en/upgrades/upgrades/migrating-from-rke-add-on
 ---

 > **Important: RKE add-on install is only supported up to Rancher v2.0.8**
@@ -1,6 +1,8 @@
 ---
 title: Upgrading to v2.0.7+ — Namespace Migration
 weight: 1040
+aliases:
+  - /rancher/v2.x/en/upgrades/upgrades/namespace-migration
 ---
 >This section applies only to Rancher upgrades from v2.0.6 or earlier to v2.0.7 or later. Upgrades from v2.0.7 to later version are unaffected.

@@ -0,0 +1,17 @@
+---
+title: Install Rancher on a Linux OS
+weight: 2
+---
+
+> This section is under construction.
+
+Rancher is both a platform and a Kubernetes distribution. In this section you'll learn how to install the Rancher binary. You will use the Rancher CLI to set up a Rancher Kubernetes cluster that has the Rancher server Helm chart preinstalled.
+
+There are two main ways that Rancher can be installed:
+
+1. You can use Helm to install the Rancher Helm chart on any Kubernetes cluster.
+2. You can use the Rancher CLI to install a Rancher Kubernetes cluster. This cluster comes with the Rancher Helm chart built in.
+
+The installation path that you choose will affect the way that you upgrade Rancher, but not the way that Rancher is backed up and restored.
+
+This section focuses on the installation path in which the Rancher Helm chart is installed on an existing Kubernetes cluster.
@@ -0,0 +1,10 @@
+---
+title: Install
+weight: 1
+---
+
+> This page is under construction.
+
+In this section, you'll learn how to create a Rancher Kubernetes cluster that comes with the Rancher Helm chart built in.
+
+> To install Rancher on an existing Kubernetes cluster, refer to the instructions on [installing the Rancher Helm chart.](../../rancher-helm-install-upgrade/installation)
@@ -0,0 +1,28 @@
+---
+title: Upgrades and Rollbacks
+weight: 2
+---
+
+> This page is under construction.
+
+This page is about how to upgrade the local Kubernetes cluster that Rancher is installed on, as well as the Rancher Helm chart.
+
+This information applies if you set up the local Rancher server cluster using the Rancher CLI.
+
+To upgrade the Rancher server's local Kubernetes cluster using the Rancher CLI, you will first upgrade the master nodes of the cluster, and then the worker nodes.
+
+### About Rancher Kubernetes
+
+Rancher is intended to be installed on any Kubernetes cluster.
+
+The Rancher CLI comes with a Kubernetes distribution called Rancher Kubernetes, which allows you to install Kubernetes more easily as a prerequisite to installing Rancher.
+
+Rancher Kubernetes clusters can also be imported into Rancher.
+
+
+### Known Upgrade Issues
+
+A list of known issues for each Rancher version can be found in the release notes on [GitHub](https://github.com/rancher/rancher/releases) and on the [Rancher forums.](https://forums.rancher.com/c/announcements/12)
+
+### Caveats
+Upgrades _to_ or _from_ any chart in the [rancher-alpha repository]({{<baseurl>}}/rancher/v2.x/en/installation/options/server-tags/#helm-chart-repositories/) aren't supported.
@@ -0,0 +1,8 @@
+---
+title: Cluster Upgrade
+weight: 2
+---
+
+> This section is under construction.
+
+In this section, you'll learn how to upgrade the Rancher Helm chart and the master nodes of the Rancher Kubernetes cluster, if applicable.
@@ -0,0 +1,8 @@
+---
+title: Worker Node Upgrade
+weight: 1
+---
+
+> This page is under construction.
+
+In this section, you'll learn how to upgrade the worker nodes of the Rancher Kubernetes cluster, if applicable.
@@ -0,0 +1,6 @@
+---
+title: Upgrade the Rancher Image
+weight: 1
+---
+
+> This page is under construction.
@@ -0,0 +1,4 @@
+---
+title: Rollbacks
+weight: 3
+---
@@ -1,52 +0,0 @@
---
-title: Installing Rancher on a Kubernetes Cluster
-weight: 3
-description: For production environments, install Rancher in a high-availability configuration. Read the guide for setting up a 3-node cluster and still install Rancher using a Helm chart.
-aliases:
-  - /rancher/v2.x/en/installation/ha/
---
-
-For production environments, we recommend installing Rancher in a high-availability configuration so that your user base can always access Rancher Server. When installed in a Kubernetes cluster, Rancher will integrate with the cluster's etcd database and take advantage of Kubernetes scheduling for high-availability.
-
-This section describes how to create and manage a Kubernetes cluster, then install Rancher onto that cluster. For this type of architecture, you will need to deploy nodes - typically virtual machines - in the infrastructure provider of your choice. You will also need to configure a load balancer to direct front-end traffic to the three VMs. When the VMs are running and fulfill the [node requirements,]({{<baseurl>}}/rancher/v2.x/en/installation/requirements) you can use RKE or K3s to deploy Kubernetes onto them, then use the Helm package manager to deploy Rancher onto Kubernetes.
-
-### Optional: Installing Rancher on a Single-node Kubernetes Cluster
-
-If you only have one node, but you want to use the Rancher server in production in the future, it is better to install Rancher on a single-node Kubernetes cluster than to install it with Docker.
-
-One option is to install Rancher with Helm on a Kubernetes cluster, but to only use a single node in the cluster. In this case, the Rancher server does not have high availability, which is important for running Rancher in production. However, this option is useful if you want to save resources by using a single node in the short term, while preserving a high-availability migration path. In the future, you can add nodes to the cluster to get a high-availability Rancher server.
-
-To set up a single-node RKE cluster, configure only one node in the `cluster.yml` . The single node should have all three roles: `etcd`, `controlplane`, and `worker`.
-
-To set up a single-node K3s cluster, run the Rancher server installation command on just one node instead of two nodes.
-
-In both single-node Kubernetes setups, Rancher can be installed with Helm on the Kubernetes cluster in the same way that it would be installed on any other cluster.
-
-### Important Notes on Architecture
-
-The Rancher management server can only be run on Kubernetes cluster in an infrastructure provider where Kubernetes is installed using K3s or RKE. Use of Rancher on hosted Kubernetes providers, such as EKS, is not supported.
-
-For the best performance and security, we recommend a dedicated Kubernetes cluster for the Rancher management server. Running user workloads on this cluster is not advised. After deploying Rancher, you can [create or import clusters]({{<baseurl>}}/rancher/v2.x/en/cluster-provisioning/#cluster-creation-in-rancher) for running your workloads.
-
-For information on how Rancher works, regardless of the installation method, refer to the [architecture section.]({{<baseurl>}}/rancher/v2.x/en/overview/architecture)
-
-## Installation Outline
-
- [Set up Infrastructure]({{<baseurl>}}/rancher/v2.x/en/installation/k8s-install/create-nodes-lb/)
- [Set up a Kubernetes Cluster]({{<baseurl>}}/rancher/v2.x/en/installation/k8s-install/kubernetes-rke/)
- [Install Rancher]({{<baseurl>}}/rancher/v2.x/en/installation/k8s-install/helm-rancher/)
-
-## Additional Install Options
-
- [Migrating from a high-availability Kubernetes Install with an RKE Add-on]({{<baseurl>}}/rancher/v2.x/en/upgrades/upgrades/migrating-from-rke-add-on/)
- [Installing Rancher with Helm 2:]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2) This section provides a copy of the older high-availability Rancher installation instructions that used Helm 2, and it is intended to be used if upgrading to Helm 3 is not feasible.
-
-## Previous Methods
-
-[RKE add-on install]({{<baseurl>}}/rancher/v2.x/en/installation/options/rke-add-on/)
-
-> **Important: RKE add-on install is only supported up to Rancher v2.0.8**
->
-> Please use the Rancher Helm chart to install Rancher on a Kubernetes cluster. For details, see the [Kubernetes Install - Installation Outline]({{<baseurl>}}/rancher/v2.x/en/installation/k8s-install/#installation-outline).
->
-> If you are currently using the RKE add-on install method, see [Migrating from a Kubernetes Install with an RKE Add-on]({{<baseurl>}}/rancher/v2.x/en/upgrades/upgrades/migrating-from-rke-add-on/) for details on how to move to using the helm chart.
@@ -1,130 +0,0 @@
---
-title: '1. Set up Infrastructure'
-weight: 185
-aliases:
-  - /rancher/v2.x/en/installation/ha/create-nodes-lb
---
-
-In this section, you will provision the underlying infrastructure for your Rancher management server.
-
-The recommended infrastructure for the Rancher-only Kubernetes cluster differs depending on whether Rancher will be installed on a K3s Kubernetes cluster, an RKE Kubernetes cluster, or a single Docker container.
-
-For more information about each installation option, refer to [this page.]({{<baseurl>}}/rancher/v2.x/en/installation)
-
-> **Note:** These nodes must be in the same region. You may place these servers in separate availability zones (datacenter).
-
-{{% tabs %}}
-{{% tab "K3s" %}}
-To install the Rancher management server on a high-availability K3s cluster, we recommend setting up the following infrastructure:
-
- **Two Linux nodes,** typically virtual machines, in the infrastructure provider of your choice.
- **An external database** to store the cluster data. We recommend MySQL.
- **A load balancer** to direct traffic to the two 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
-
-Make sure that your nodes fulfill the general installation requirements for [OS, container runtime, hardware, and networking.]({{<baseurl>}}/rancher/v2.x/en/installation/requirements/)
-
-For an example of one way to set up Linux nodes, refer to this [tutorial]({{<baseurl>}}/rancher/v2.x/en/installation/options/ec2-node) for setting up nodes as instances in Amazon EC2.
-
-### 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.
-
-For a high-availability K3s installation, you will need to set a [MySQL](https://www.mysql.com/) external database. Rancher has been tested on K3s Kubernetes clusters using MySQL version 5.7 as the datastore.
-
-When you install Kubernetes using the K3s installation script, you will pass in details for K3s to connect to the database.
-
-For an example of one way to set up the MySQL database, refer to this [tutorial]({{<baseurl>}}/rancher/v2.x/en/installation/options/rds/) for setting up MySQL on Amazon's RDS service.
-
-For the complete list of options that are available for configuring a K3s cluster datastore, refer to the [K3s documentation.]({{<baseurl>}}/k3s/latest/en/installation/datastore/)
-
-### 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.
-
-When Kubernetes gets set up in a later step, the K3s tool will deploy a Traefik Ingress controller. This controller will listen on ports 80 and 443 of the worker nodes, answering traffic destined for specific hostnames.
-
-When Rancher is installed (also in a later step), the Rancher system creates an Ingress resource. That Ingress tells the Traefik Ingress controller to listen for traffic destined for the Rancher hostname. The Traefik Ingress controller, when receiving traffic destined for the Rancher hostname, will forward that traffic to the running Rancher pods in the cluster.
-
-For your implementation, consider if you want or need to use a Layer-4 or Layer-7 load balancer:
-
- **A layer-4 load balancer** is the simpler of the two choices, in which you are forwarding TCP traffic to your nodes. We recommend configuring your load balancer as a Layer 4 balancer, forwarding traffic to ports TCP/80 and TCP/443 to the Rancher management cluster nodes. The Ingress controller on the cluster will redirect HTTP traffic to HTTPS and terminate SSL/TLS on port TCP/443. The Ingress controller will forward traffic to port TCP/80 to the Ingress pod in the Rancher deployment.
- **A layer-7 load balancer** is a bit more complicated but can offer features that you may want. For instance, a layer-7 load balancer is capable of handling TLS termination at the load balancer, as opposed to Rancher doing TLS termination itself. This can be beneficial if you want to centralize your TLS termination in your infrastructure. Layer-7 load balancing also offers the capability for your load balancer to make decisions based on HTTP attributes such as cookies, etc. that a layer-4 load balancer is not able to concern itself with. If you decide to terminate the SSL/TLS traffic on a layer-7 load balancer, you will need to use the `--set tls=external` option when installing Rancher in a later step. For more information, refer to the [Rancher Helm chart options.]({{<baseurl>}}/rancher/v2.x/en/installation/options/chart-options/#external-tls-termination)
-
-For an example showing how to set up an NGINX load balancer, refer to [this page.]({{<baseurl>}}/rancher/v2.x/en/installation/options/nginx/)
-
-For a how-to guide for setting up an Amazon ELB Network Load Balancer, refer to [this page.]({{<baseurl>}}/rancher/v2.x/en/installation/options/nlb/)
-
-> **Important:**
-> Do not use this load balancer (i.e, the `local` cluster Ingress) to load balance applications other than Rancher following installation. Sharing this Ingress with other applications may result in websocket errors to Rancher following Ingress configuration reloads for other apps. We recommend dedicating the `local` cluster to Rancher and no other applications.
-
-### 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.
-
-Depending on your environment, this may be an A record pointing to the load balancer IP, or it may be a CNAME pointing to the load balancer hostname. In either case, make sure this record is the hostname that you intend Rancher to respond on.
-
-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)
-
-
-
-{{% /tab %}}
-{{% tab "RKE" %}}
-To install the Rancher management server on a high-availability RKE cluster, we recommend setting up the following infrastructure:
-
- **Three Linux nodes,** typically virtual machines, in an infrastructure provider such as Amazon's EC2, Google Compute Engine, or vSphere.
- **A load balancer** to direct front-end traffic to the three 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.
-
-These nodes must be in the same region/data center. You may place these servers in separate availability zones.
-
-### 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
-
-Make sure that your nodes fulfill the general installation requirements for [OS, container runtime, hardware, and networking.]({{<baseurl>}}/rancher/v2.x/en/installation/requirements/)
-
-For an example of one way to set up Linux nodes, refer to this [tutorial]({{<baseurl>}}/rancher/v2.x/en/installation/options/ec2-node/) for setting up nodes as instances in Amazon EC2.
-
-### 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.
-
-When Kubernetes gets set up in a later step, the RKE tool will deploy an NGINX Ingress controller. This controller will listen on ports 80 and 443 of the worker nodes, answering traffic destined for specific hostnames.
-
-When Rancher is installed (also in a later step), the Rancher system creates an Ingress resource. That Ingress tells the NGINX Ingress controller to listen for traffic destined for the Rancher hostname. The NGINX Ingress controller, when receiving traffic destined for the Rancher hostname, will forward that traffic to the running Rancher pods in the cluster.
-
-For your implementation, consider if you want or need to use a Layer-4 or Layer-7 load balancer:
-
- **A layer-4 load balancer** is the simpler of the two choices, in which you are forwarding TCP traffic to your nodes. We recommend configuring your load balancer as a Layer 4 balancer, forwarding traffic to ports TCP/80 and TCP/443 to the Rancher management cluster nodes. The Ingress controller on the cluster will redirect HTTP traffic to HTTPS and terminate SSL/TLS on port TCP/443. The Ingress controller will forward traffic to port TCP/80 to the Ingress pod in the Rancher deployment.
- **A layer-7 load balancer** is a bit more complicated but can offer features that you may want. For instance, a layer-7 load balancer is capable of handling TLS termination at the load balancer, as opposed to Rancher doing TLS termination itself. This can be beneficial if you want to centralize your TLS termination in your infrastructure. Layer-7 load balancing also offers the capability for your load balancer to make decisions based on HTTP attributes such as cookies, etc. that a layer-4 load balancer is not able to concern itself with. If you decide to terminate the SSL/TLS traffic on a layer-7 load balancer, you will need to use the `--set tls=external` option when installing Rancher in a later step. For more information, refer to the [Rancher Helm chart options.]({{<baseurl>}}/rancher/v2.x/en/installation/options/chart-options/#external-tls-termination)
-
-For an example showing how to set up an NGINX load balancer, refer to [this page.]({{<baseurl>}}/rancher/v2.x/en/installation/options/nginx/)
-
-For a how-to guide for setting up an Amazon ELB Network Load Balancer, refer to [this page.]({{<baseurl>}}/rancher/v2.x/en/installation/options/nlb/)
-
-> **Important:**
-> Do not use this load balancer (i.e, the `local` cluster Ingress) to load balance applications other than Rancher following installation. Sharing this Ingress with other applications may result in websocket errors to Rancher following Ingress configuration reloads for other apps. We recommend dedicating the `local` cluster to Rancher and no other applications.
-
-### 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.
-
-Depending on your environment, this may be an A record pointing to the LB IP, or it may be a CNAME pointing to the load balancer hostname. In either case, make sure this record is the hostname that you intend Rancher to respond on.
-
-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)
-
-{{% /tab %}}
-{{% /tabs %}}
-
-### [Next: Set up a Kubernetes Cluster]({{<baseurl>}}/rancher/v2.x/en/installation/k8s-install/kubernetes-rke/)
@@ -1,43 +0,0 @@
---
-title: Installing Rancher in an Air Gapped Environment with Helm 2
-weight: 2
-aliases:
-  - /rancher/v2.x/en/installation/air-gap-installation/
-  - /rancher/v2.x/en/installation/air-gap-high-availability/
-  - /rancher/v2.x/en/installation/air-gap-single-node/
---
-
-> After Helm 3 was released, the Rancher installation instructions were updated to use Helm 3.
->
-> If you are using Helm 2, we recommend [migrating to Helm 3](https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/) because it is simpler to use and more secure than Helm 2.
->
-> This section provides a copy of the older instructions for installing Rancher on a Kubernetes cluster using Helm 2 in an air air gap environment, and it is intended to be used if upgrading to Helm 3 is not feasible.
-
-This section is about installations of Rancher server in an air gapped environment. An air gapped environment could be where Rancher server will be installed offline, behind a firewall, or behind a proxy.
-
-Throughout the installations instructions, there will be _tabs_ for either a high availability Kubernetes installation or a single-node Docker installation.
-
-### Air Gapped Kubernetes Installations
-
-This section covers how to install Rancher on a Kubernetes cluster in an air gapped environment.
-
-A Kubernetes installation is comprised of three nodes running the Rancher server components on a Kubernetes cluster. The persistence layer (etcd) is also replicated on these three nodes, providing redundancy and data duplication in case one of the nodes fails.
-
-### Air Gapped Docker Installations
-
-These instructions also cover how to install Rancher on a single node in an air gapped environment.
-
-The Docker installation is for Rancher users that are wanting to test out Rancher. Instead of running on a Kubernetes cluster, you install the Rancher server component on a single node using a `docker run` command. Since there is only one node and a single Docker container, if the node goes down, there is no copy of the etcd data available on other nodes and you will lose all the data of your Rancher server.
-
-> **Important:** If you install Rancher following the Docker installation guide, there is no upgrade path to transition your Docker Installation to a Kubernetes Installation.
-
-Instead of running the Docker installation, you have the option to follow the Kubernetes Install guide, but only use one node to install Rancher. Afterwards, you can scale up the etcd nodes in your Kubernetes cluster to make it a Kubernetes Installation.
-
-# Installation Outline
-
- [1. Prepare your Node(s)]({{<baseurl>}}/rancher/v2.x/en/installation/other-installation-methods/air-gap/prepare-nodes/)
- [2. Collect and Publish Images to your Private Registry]({{<baseurl>}}/rancher/v2.x/en/installation/other-installation-methods/air-gap/populate-private-registry/)
- [3. Launch a Kubernetes Cluster with RKE]({{<baseurl>}}/rancher/v2.x/en/installation/other-installation-methods/air-gap/launch-kubernetes/)
- [4. Install Rancher]({{<baseurl>}}/rancher/v2.x/en/installation/other-installation-methods/air-gap/install-rancher/)
-
-### [Next: Prepare your Node(s)]({{<baseurl>}}/rancher/v2.x/en/installation/other-installation-methods/air-gap/prepare-nodes/)
@@ -1,333 +0,0 @@
---
-title: 4. Install Rancher
-weight: 400
-aliases:
-  - /rancher/v2.x/en/installation/air-gap-installation/install-rancher/
-  - /rancher/v2.x/en/installation/air-gap-high-availability/config-rancher-system-charts/
-  - /rancher/v2.x/en/installation/air-gap-high-availability/config-rancher-for-private-reg/
-  - /rancher/v2.x/en/installation/air-gap-single-node/install-rancher
-  - /rancher/v2.x/en/installation/air-gap/install-rancher
---
-
-This section is about how to deploy Rancher for your air gapped environment. An air gapped environment could be where Rancher server will be installed offline, behind a firewall, or behind a proxy. There are _tabs_ for either a high availability (recommended) or a Docker installation.
-
-{{% tabs %}}
-{{% tab "Kubernetes Install (Recommended)" %}}
-
-Rancher recommends installing Rancher on a Kubernetes cluster. A highly available Kubernetes Installation is comprised of three nodes running the Rancher server components on a Kubernetes cluster. The persistence layer (etcd) is also replicated on these three nodes, providing redundancy and data duplication in case one of the nodes fails.
-
-This section describes installing Rancher in five parts:
-
- [A. Add the Helm Chart Repository](#a-add-the-helm-chart-repository)
- [B. Choose your SSL Configuration](#b-choose-your-ssl-configuration)
- [C. Render the Rancher Helm Template](#c-render-the-rancher-helm-template)
- [D. Install Rancher](#d-install-rancher)
- [E. For Rancher versions prior to v2.3.0, Configure System Charts](#e-for-rancher-versions-prior-to-v2-3-0-configure-system-charts)
-
-### A. Add the Helm Chart Repository
-
-From a system that has access to the internet, fetch the latest Helm chart and copy the resulting manifests to a system that has access to the Rancher server cluster.
-
-1. If you haven't already, initialize `helm` locally on a workstation that has internet access. Note: Refer to the [Helm version requirements]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm-version) to choose a version of Helm to install Rancher.
-    ```plain
-    helm init -c
-    ```
-
-2. Use `helm repo add` command to add the Helm chart repository that contains charts to install Rancher. For more information about the repository choices and which is best for your use case, see [Choosing a Version of Rancher]({{<baseurl>}}/rancher/v2.x/en/installation/options/server-tags/#helm-chart-repositories).
-  {{< release-channel >}}
-    ```
-    helm repo add rancher-<CHART_REPO> https://releases.rancher.com/server-charts/<CHART_REPO>
-    ```
-
-3. Fetch the latest Rancher chart. This will pull down the chart and save it in the current directory as a `.tgz` file.
-```plain
-helm fetch rancher-<CHART_REPO>/rancher
-```
-
-> Want additional options? Need help troubleshooting? See [Kubernetes Install: Advanced Options]({{<baseurl>}}/rancher/v2.x/en/installation/k8s-install/helm-rancher/#advanced-configurations).
-
-### B. Choose your SSL Configuration
-
-Rancher Server is designed to be secure by default and requires SSL/TLS configuration.
-
-When Rancher is installed on an air gapped Kubernetes cluster, there are two recommended options for the source of the certificate.
-
-> **Note:** If you want terminate SSL/TLS externally, see [TLS termination on an External Load Balancer]({{<baseurl>}}/rancher/v2.x/en/installation/options/chart-options/#external-tls-termination).
-
-| Configuration                              | Chart option                 | Description                                                                                                                                                 | Requires cert-manager |
-| ------------------------------------------ | ---------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------- |
-| Rancher Generated Self-Signed Certificates | `ingress.tls.source=rancher` | Use certificates issued by Rancher's generated CA (self signed)<br> This is the **default** and does not need to be added when rendering the Helm template. | yes                   |
-| Certificates from Files                    | `ingress.tls.source=secret`  | Use your own certificate files by creating Kubernetes Secret(s). <br> This option must be passed when rendering the Rancher Helm template.                  | no                    |
-
-### C. Render the Rancher Helm Template
-
-When setting up the Rancher Helm template, there are several options in the Helm chart that are designed specifically for air gap installations.
-
-| Chart Option            | Chart Value                      | Description   |
-| ----------------------- | -------------------------------- | ---- |
-| `certmanager.version` | "<version>" | Configure proper Rancher TLS issuer depending of running cert-manager version. |
-| `systemDefaultRegistry` | `<REGISTRY.YOURDOMAIN.COM:PORT>` | Configure Rancher server to always pull from your private registry when provisioning clusters.  |
-| `useBundledSystemChart` | `true`                           | Configure Rancher server to use the packaged copy of Helm system charts. The [system charts](https://github.com/rancher/system-charts) repository contains all the catalog items required for features such as monitoring, logging, alerting and global DNS. These [Helm charts](https://github.com/rancher/system-charts) are located in GitHub, but since you are in an air gapped environment, using the charts that are bundled within Rancher is much easier than setting up a Git mirror. _Available as of v2.3.0_ |
-
-Based on the choice your made in [B. Choose your SSL Configuration](#b-choose-your-ssl-configuration), complete one of the procedures below.
-
-{{% accordion id="self-signed" label="Option A-Default Self-Signed Certificate" %}}
-
-By default, Rancher generates a CA and uses cert-manager to issue the certificate for access to the Rancher server interface.
-
-> **Note:**
-> Recent changes to cert-manager require an upgrade. If you are upgrading Rancher and using a version of cert-manager older than v0.11.0, please see our [upgrade cert-manager documentation]({{<baseurl>}}/rancher/v2.x/en/installation/options/upgrading-cert-manager/).
-
-1. From a system connected to the internet, add the cert-manager repo to Helm.
-    ```plain
-    helm repo add jetstack https://charts.jetstack.io
-    helm repo update
-    ```
-
-1. Fetch the latest cert-manager chart available from the [Helm chart repository](https://hub.helm.sh/charts/jetstack/cert-manager).
-
-   ```plain
-   helm fetch jetstack/cert-manager --version v0.12.0
-   ```
-
-1. Render the cert manager template with the options you would like to use to install the chart. Remember to set the `image.repository` option to pull the image from your private registry. This will create a `cert-manager` directory with the Kubernetes manifest files.
-   ```plain
-   helm template ./cert-manager-v0.12.0.tgz --output-dir . \
-       --name cert-manager --namespace cert-manager \
-       --set image.repository=<REGISTRY.YOURDOMAIN.COM:PORT>/quay.io/jetstack/cert-manager-controller
-       --set webhook.image.repository=<REGISTRY.YOURDOMAIN.COM:PORT>/quay.io/jetstack/cert-manager-webhook
-       --set cainjector.image.repository=<REGISTRY.YOURDOMAIN.COM:PORT>/quay.io/jetstack/cert-manager-cainjector
-   ```
-
-1. Download the required CRD file for cert-manager
-   ```plain
-   curl -L -o cert-manager/cert-manager-crd.yaml https://raw.githubusercontent.com/jetstack/cert-manager/release-0.12/deploy/manifests/00-crds.yaml
-   ```
-1. Render the Rancher template, declaring your chosen options. Use 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.
-
-
-    Placeholder | Description
-    ------------|-------------
-    `<VERSION>` | The version number of the output tarball.
-    `<RANCHER.YOURDOMAIN.COM>` | The DNS name you pointed at your load balancer.
-    `<REGISTRY.YOURDOMAIN.COM:PORT>` | The DNS name for your private registry.
-    `<CERTMANAGER_VERSION>` | Cert-manager version running on k8s cluster.
-
-     ```plain
-    helm template ./rancher-<VERSION>.tgz --output-dir . \
-     --name rancher \
-     --namespace cattle-system \
-     --set hostname=<RANCHER.YOURDOMAIN.COM> \
-     --set certmanager.version=<CERTMANAGER_VERSION> \
-     --set rancherImage=<REGISTRY.YOURDOMAIN.COM:PORT>/rancher/rancher \
-     --set systemDefaultRegistry=<REGISTRY.YOURDOMAIN.COM:PORT> \ # Available as of v2.2.0, set a default private registry to be used in Rancher
-     --set useBundledSystemChart=true # Available as of v2.3.0, use the packaged Rancher system charts
-```
-
-{{% /accordion %}}
-
-{{% accordion id="secret" label="Option B: Certificates From Files using Kubernetes 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.
-
-Render the Rancher template, declaring your chosen options. Use 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.
-
-| Placeholder                      | Description                                     |
-| -------------------------------- | ----------------------------------------------- |
-| `<VERSION>`                      | The version number of the output tarball.       |
-| `<RANCHER.YOURDOMAIN.COM>`       | The DNS name you pointed at your load balancer. |
-| `<REGISTRY.YOURDOMAIN.COM:PORT>` | The DNS name for your private registry.         |
-
-```plain
-   helm template ./rancher-<VERSION>.tgz --output-dir . \
-    --name rancher \
-    --namespace cattle-system \
-    --set hostname=<RANCHER.YOURDOMAIN.COM> \
-    --set rancherImage=<REGISTRY.YOURDOMAIN.COM:PORT>/rancher/rancher \
-    --set ingress.tls.source=secret \
-    --set systemDefaultRegistry=<REGISTRY.YOURDOMAIN.COM:PORT> \ # Available as of v2.2.0, set a default private registry to be used in Rancher
-    --set useBundledSystemChart=true # Available as of v2.3.0, use the packaged Rancher system charts
-```
-
-If you are using a Private CA signed cert, add `--set privateCA=true` following `--set ingress.tls.source=secret`:
-
-```plain
-   helm template ./rancher-<VERSION>.tgz --output-dir . \
-    --name rancher \
-    --namespace cattle-system \
-    --set hostname=<RANCHER.YOURDOMAIN.COM> \
-    --set rancherImage=<REGISTRY.YOURDOMAIN.COM:PORT>/rancher/rancher \
-    --set ingress.tls.source=secret \
-    --set privateCA=true \
-    --set systemDefaultRegistry=<REGISTRY.YOURDOMAIN.COM:PORT> \ # Available as of v2.2.0, set a default private registry to be used in Rancher
-    --set useBundledSystemChart=true # Available as of v2.3.0, use the packaged Rancher system charts
-```
-
-Then refer to [Adding TLS Secrets]({{<baseurl>}}/rancher/v2.x/en/installation/options/tls-secrets/) to publish the certificate files so Rancher and the ingress controller can use them.
-
-{{% /accordion %}}
-
-### D. Install Rancher
-
-Copy the rendered manifest directories to a system that has access to the Rancher server cluster to complete installation.
-
-Use `kubectl` to create namespaces and apply the rendered manifests.
-
-If you chose to use self-signed certificates in [B. Choose your SSL Configuration](#b-choose-your-ssl-configuration), install cert-manager.
-
-{{% accordion id="install-cert-manager" label="Self-Signed Certificate Installs - Install Cert-manager" %}}
-
-If you are using self-signed certificates, install cert-manager:
-
-1. Create the namespace for cert-manager.
-```plain
-kubectl create namespace cert-manager
-```
-
-1. Create the cert-manager CustomResourceDefinitions (CRDs).
-```plain
-kubectl apply -f cert-manager/cert-manager-crd.yaml
-```
-
-> **Important:**
-> If you are running Kubernetes v1.15 or below, you will need to add the `--validate=false flag to your kubectl apply command above else you will receive a validation error relating to the x-kubernetes-preserve-unknown-fields field in cert-manager’s CustomResourceDefinition resources. This is a benign error and occurs due to the way kubectl performs resource validation.
-
-1. Launch cert-manager.
-```plain
-kubectl apply -R -f ./cert-manager
-```
-
-{{% /accordion %}}
-
-Install Rancher:
-
-```plain
-kubectl create namespace cattle-system
-kubectl -n cattle-system apply -R -f ./rancher
-```
-
-**Step Result:** If you are installing Rancher v2.3.0+, the installation is complete.
-
-### E. For Rancher versions prior to v2.3.0, Configure System Charts
-
-If you are installing Rancher versions prior to v2.3.0, you will not be able to use the packaged system charts. Since the Rancher system charts are hosted in Github, an air gapped installation will not be able to access these charts. Therefore, you must [configure the Rancher system charts]({{<baseurl>}}/rancher/v2.x/en/installation/options/local-system-charts/#setting-up-system-charts-for-rancher-prior-to-v2-3-0).
-
-### Additional Resources
-
-These resources could be helpful when installing Rancher:
-
- [Rancher Helm chart options]({{<baseurl>}}/rancher/v2.x/en/installation/options/chart-options/)
- [Adding TLS secrets]({{<baseurl>}}/rancher/v2.x/en/installation/options/tls-secrets/)
- [Troubleshooting Rancher Kubernetes Installations]({{<baseurl>}}/rancher/v2.x/en/installation/options/troubleshooting/)
-
-{{% /tab %}}
-{{% tab "Docker Install" %}}
-
-The Docker installation is for Rancher users that are wanting to **test** out Rancher. Instead of running on a Kubernetes cluster, you install the Rancher server component on a single node using a `docker run` command. Since there is only one node and a single Docker container, if the node goes down, there is no copy of the etcd data available on other nodes and you will lose all the data of your Rancher server. **Important: If you install Rancher following the Docker installation guide, there is no upgrade path to transition your Docker installation to a Kubernetes Installation.** Instead of running the single node installation, you have the option to follow the Kubernetes Install guide, but only use one node to install Rancher. Afterwards, you can scale up the etcd nodes in your Kubernetes cluster to make it a Kubernetes Installation.
-
-For security purposes, SSL (Secure Sockets Layer) is required when using Rancher. SSL secures all Rancher network communication, like when you login or interact with a cluster.
-
-| Environment Variable Key         | Environment Variable Value       | Description     |
-| -------------------------------- | -------------------------------- | ---- |
-| `CATTLE_SYSTEM_DEFAULT_REGISTRY` | `<REGISTRY.YOURDOMAIN.COM:PORT>` | Configure Rancher server to always pull from your private registry when provisioning clusters.  |
-| `CATTLE_SYSTEM_CATALOG`          | `bundled`                        | Configure Rancher server to use the packaged copy of Helm system charts. The [system charts](https://github.com/rancher/system-charts) repository contains all the catalog items required for features such as monitoring, logging, alerting and global DNS. These [Helm charts](https://github.com/rancher/system-charts) are located in GitHub, but since you are in an air gapped environment, using the charts that are bundled within Rancher is much easier than setting up a Git mirror. _Available as of v2.3.0_ |
-
-> **Do you want to...**
->
-> - Configure custom CA root certificate to access your services? See [Custom CA root certificate]({{<baseurl>}}/rancher/v2.x/en/installation/options/chart-options/#additional-trusted-cas).
-> - Record all transactions with the Rancher API? See [API Auditing]({{<baseurl>}}/rancher/v2.x/en/installation/other-installation-methods/single-node-docker/#api-audit-log).
-
- For Rancher prior to v2.3.0, you will need to mirror the `system-charts` repository to a location in your network that Rancher can reach. Then, after Rancher is installed, you will need to configure Rancher to use that repository. For details, refer to the documentation on [setting up the system charts for Rancher prior to v2.3.0.]({{<baseurl>}}/rancher/v2.x/en/installation/options/local-system-charts/#setting-up-system-charts-for-rancher-prior-to-v2-3-0)
-
-Choose from the following options:
-
-{{% accordion id="option-a" label="Option A-Default Self-Signed Certificate" %}}
-
-If you are installing Rancher in a development or testing environment where identity verification isn't a concern, install Rancher using the self-signed certificate that it generates. This installation option omits the hassle of generating a certificate yourself.
-
-Log into your Linux host, and then run the installation command below. When entering the command, use the table below to replace each placeholder.
-
-| Placeholder                      | Description                                                                                                                   |
-| -------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
-| `<REGISTRY.YOURDOMAIN.COM:PORT>` | Your private registry URL and port.                                                                                           |
-| `<RANCHER_VERSION_TAG>`          | The release tag of the [Rancher version]({{<baseurl>}}/rancher/v2.x/en/installation/options/server-tags/) that you want to install. |
-
-```
-docker run -d --restart=unless-stopped \
-    -p 80:80 -p 443:443 \
-    -e CATTLE_SYSTEM_DEFAULT_REGISTRY=<REGISTRY.YOURDOMAIN.COM:PORT> \ # Set a default private registry to be used in Rancher
-    -e CATTLE_SYSTEM_CATALOG=bundled \ #Available as of v2.3.0, use the packaged Rancher system charts
-    <REGISTRY.YOURDOMAIN.COM:PORT>/rancher/rancher:<RANCHER_VERSION_TAG>
-```
-
-{{% /accordion %}}
-{{% accordion id="option-b" label="Option B-Bring Your Own Certificate: Self-Signed" %}}
-
-In development or testing environments where your team will access your Rancher server, create a self-signed certificate for use with your install so that your team can verify they're connecting to your instance of Rancher.
-
-> **Prerequisites:**
-> From a computer with an internet connection, create a self-signed certificate using [OpenSSL](https://www.openssl.org/) or another method of your choice.
->
-> - The certificate files must be in [PEM format]({{<baseurl>}}/rancher/v2.x/en/installation/other-installation-methods/single-node-docker/#pem).
-> - In your certificate file, include all intermediate certificates in the chain. Order your certificates with your certificate first, followed by the intermediates. For an example, see [SSL FAQ / Troubleshooting]({{<baseurl>}}/rancher/v2.x/en/installation/other-installation-methods/single-node-docker/#cert-order).
-
-After creating your certificate, log into your Linux host, and then run the installation command below. When entering the command, use the table below to replace each placeholder. Use the `-v` flag and provide the path to your certificates to mount them in your container.
-
-| Placeholder                      | Description                                                                                                                   |
-| -------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
-| `<CERT_DIRECTORY>`               | The path to the directory containing your certificate files.                                                                  |
-| `<FULL_CHAIN.pem>`               | The path to your full certificate chain.                                                                                      |
-| `<PRIVATE_KEY.pem>`              | The path to the private key for your certificate.                                                                             |
-| `<CA_CERTS.pem>`                     | The path to the certificate authority's certificate.                                                                          |
-| `<REGISTRY.YOURDOMAIN.COM:PORT>` | Your private registry URL and port.                                                                                           |
-| `<RANCHER_VERSION_TAG>`          | The release tag of the [Rancher version]({{<baseurl>}}/rancher/v2.x/en/installation/options/server-tags/) that you want to install. |
-
-```
-docker run -d --restart=unless-stopped \
-    -p 80:80 -p 443:443 \
-    -v /<CERT_DIRECTORY>/<FULL_CHAIN.pem>:/etc/rancher/ssl/cert.pem \
-    -v /<CERT_DIRECTORY>/<PRIVATE_KEY.pem>:/etc/rancher/ssl/key.pem \
-    -v /<CERT_DIRECTORY>/<CA_CERTS.pem>:/etc/rancher/ssl/cacerts.pem \
-    -e CATTLE_SYSTEM_DEFAULT_REGISTRY=<REGISTRY.YOURDOMAIN.COM:PORT> \ # Set a default private registry to be used in Rancher
-    -e CATTLE_SYSTEM_CATALOG=bundled \ #Available as of v2.3.0, use the packaged Rancher system charts
-    <REGISTRY.YOURDOMAIN.COM:PORT>/rancher/rancher:<RANCHER_VERSION_TAG>
-```
-
-{{% /accordion %}}
-{{% accordion id="option-c" label="Option C-Bring Your Own Certificate: Signed by Recognized CA" %}}
-
-In development or testing environments where you're exposing an app publicly, use a certificate signed by a recognized CA so that your user base doesn't encounter security warnings.
-
-> **Prerequisite:** The certificate files must be in [PEM format]({{<baseurl>}}/rancher/v2.x/en/installation/other-installation-methods/single-node-docker/#pem).
-
-After obtaining your certificate, log into your Linux host, and then run the installation command below. When entering the command, use the table below to replace each placeholder. Because your certificate is signed by a recognized CA, mounting an additional CA certificate file is unnecessary.
-
-| Placeholder                      | Description                                                                                                                   |
-| -------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
-| `<CERT_DIRECTORY>`               | The path to the directory containing your certificate files.                                                                  |
-| `<FULL_CHAIN.pem>`               | The path to your full certificate chain.                                                                                      |
-| `<PRIVATE_KEY.pem>`              | The path to the private key for your certificate.                                                                             |
-| `<REGISTRY.YOURDOMAIN.COM:PORT>` | Your private registry URL and port.                                                                                           |
-| `<RANCHER_VERSION_TAG>`          | The release tag of the [Rancher version]({{<baseurl>}}/rancher/v2.x/en/installation/options/server-tags/) that you want to install. |
-
-> **Note:** Use the `--no-cacerts` as argument to the container to disable the default CA certificate generated by Rancher.
-
-```
-docker run -d --restart=unless-stopped \
-    -p 80:80 -p 443:443 \
-    --no-cacerts \
-    -v /<CERT_DIRECTORY>/<FULL_CHAIN.pem>:/etc/rancher/ssl/cert.pem \
-    -v /<CERT_DIRECTORY>/<PRIVATE_KEY.pem>:/etc/rancher/ssl/key.pem \
-    -e CATTLE_SYSTEM_DEFAULT_REGISTRY=<REGISTRY.YOURDOMAIN.COM:PORT> \ # Set a default private registry to be used in Rancher
-    -e CATTLE_SYSTEM_CATALOG=bundled \ #Available as of v2.3.0, use the packaged Rancher system charts
-    <REGISTRY.YOURDOMAIN.COM:PORT>/rancher/rancher:<RANCHER_VERSION_TAG>
-```
-
-{{% /accordion %}}
-
-If you are installing Rancher v2.3.0+, the installation is complete.
-
-If you are installing Rancher versions prior to v2.3.0, you will not be able to use the packaged system charts. Since the Rancher system charts are hosted in Github, an air gapped installation will not be able to access these charts. Therefore, you must [configure the Rancher system charts]({{<baseurl>}}/rancher/v2.x/en/installation/options/local-system-charts/#setting-up-system-charts-for-rancher-prior-to-v2-3-0).
-
-{{% /tab %}}
-{{% /tabs %}}
@@ -1,82 +0,0 @@
---
-title: '3. Install Kubernetes with RKE (Kubernetes Installs Only)'
-weight: 300
-aliases:
-  - /rancher/v2.x/en/installation/air-gap-high-availability/install-kube
---
-
-This section is about how to prepare to launch a Kubernetes cluster which is used to deploy Rancher server for your air gapped environment.
-
-Since a Kubernetes Installation requires a Kubernetes cluster, we will create a Kubernetes cluster using [Rancher Kubernetes Engine]({{<baseurl>}}/rke/latest/en/) (RKE). Before being able to start your Kubernetes cluster, you'll need to [install RKE]({{<baseurl>}}/rke/latest/en/installation/) and create a RKE config file.
-
- [A. Create an RKE Config File](#a-create-an-rke-config-file)
- [B. Run RKE](#b-run-rke)
- [C. Save Your Files](#c-save-your-files)
-
-### A. Create an RKE Config File
-
-From a system that can access ports 22/tcp and 6443/tcp on your host nodes, use the sample below to create a new file named `rancher-cluster.yml`. This file is a Rancher Kubernetes Engine configuration file (RKE config file), which is a configuration for the cluster you're deploying Rancher to.
-
-Replace values in the code sample below with help of the _RKE Options_ table. Use the IP address or DNS names of the [3 nodes]({{<baseurl>}}/rancher/v2.x/en/installation/air-gap-high-availability/provision-hosts) you created.
-
-> **Tip:** For more details on the options available, see the RKE [Config Options]({{<baseurl>}}/rke/latest/en/config-options/).
-
-<figcaption>RKE Options</figcaption>
-
-| Option             | Required             | Description                                                                             |
-| ------------------ | -------------------- | --------------------------------------------------------------------------------------- |
-| `address`          | ✓                    | The DNS or IP address for the node within the air gap network.                          |
-| `user`             | ✓                    | A user that can run docker commands.                                                    |
-| `role`             | ✓                    | List of Kubernetes roles assigned to the node.                                          |
-| `internal_address` | optional<sup>1</sup> | The DNS or IP address used for internal cluster traffic.                                |
-| `ssh_key_path`     |                      | Path to SSH private key used to authenticate to the node (defaults to `~/.ssh/id_rsa`). |
-
-> <sup>1</sup> Some services like AWS EC2 require setting the `internal_address` if you want to use self-referencing security groups or firewalls.
-
-```yaml
-nodes:
-  - address: 10.10.3.187 # node air gap network IP
-    internal_address: 172.31.7.22 # node intra-cluster IP
-    user: rancher
-    role: ['controlplane', 'etcd', 'worker']
-    ssh_key_path: /home/user/.ssh/id_rsa
-  - address: 10.10.3.254 # node air gap network IP
-    internal_address: 172.31.13.132 # node intra-cluster IP
-    user: rancher
-    role: ['controlplane', 'etcd', 'worker']
-    ssh_key_path: /home/user/.ssh/id_rsa
-  - address: 10.10.3.89 # node air gap network IP
-    internal_address: 172.31.3.216 # node intra-cluster IP
-    user: rancher
-    role: ['controlplane', 'etcd', 'worker']
-    ssh_key_path: /home/user/.ssh/id_rsa
-
-private_registries:
-  - url: <REGISTRY.YOURDOMAIN.COM:PORT> # private registry url
-    user: rancher
-    password: '*********'
-    is_default: true
-```
-
-### B. Run RKE
-
-After configuring `rancher-cluster.yml`, bring up your Kubernetes cluster:
-
-```
-rke up --config ./rancher-cluster.yml
-```
-
-### C. Save Your Files
-
-> **Important**
-> The files mentioned below are needed to maintain, troubleshoot and upgrade your cluster.
-
-Save a copy of the following files in a secure location:
-
- `rancher-cluster.yml`: The RKE cluster configuration file.
- `kube_config_rancher-cluster.yml`: The [Kubeconfig file]({{<baseurl>}}/rke/latest/en/kubeconfig/) for the cluster, this file contains credentials for full access to the cluster.
- `rancher-cluster.rkestate`: The [Kubernetes Cluster State file]({{<baseurl>}}/rke/latest/en/installation/#kubernetes-cluster-state), this file contains credentials for full access to the cluster.<br/><br/>_The Kubernetes Cluster State file is only created when using RKE v0.2.0 or higher._
-
-> **Note:** The "rancher-cluster" parts of the two latter file names are dependent on how you name the RKE cluster configuration file.
-
-### [Next: Install Rancher]({{<baseurl>}}/rancher/v2.x/en/installation/other-installation-methods/air-gap/install-rancher)
@@ -1,274 +0,0 @@
---
-title: '2. Collect and Publish Images to your Private Registry'
-weight: 200
-aliases:
-  - /rancher/v2.x/en/installation/air-gap-installation/prepare-private-reg/
-  - /rancher/v2.x/en/installation/air-gap-high-availability/prepare-private-registry/
-  - /rancher/v2.x/en/installation/air-gap-single-node/prepare-private-registry/
-  - /rancher/v2.x/en/installation/air-gap-single-node/config-rancher-for-private-reg/
-  - /rancher/v2.x/en/installation/air-gap-high-availability/config-rancher-for-private-reg/
---
-
-> **Prerequisites:** You must have a [private registry](https://docs.docker.com/registry/deploying/) available to use.
->
-> **Note:** Populating the private registry with images is the same process for HA and Docker installations, the differences in this section is based on whether or not you are planning to provision a Windows cluster or not.
-
-By default, all images used to [provision Kubernetes clusters]({{<baseurl>}}/rancher/v2.x/en/cluster-provisioning/) or launch any [tools]({{<baseurl>}}/rancher/v2.x/en/cluster-admin/tools/) in Rancher, e.g. monitoring, pipelines, alerts, are pulled from Docker Hub. In an air gap installation of Rancher, you will need a private registry that is located somewhere accessible by your Rancher server. Then, you will load the registry with all the images.
-
-This section describes how to set up your private registry so that when you install Rancher, Rancher will pull all the required images from this registry.
-
-By default, we provide the steps of how to populate your private registry assuming you are provisioning Linux only clusters, but if you plan on provisioning any [Windows clusters]({{<baseurl>}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/windows-clusters/), there are separate instructions to support the images needed for a Windows cluster.
-
-{{% tabs %}}
-{{% tab "Linux Only Clusters" %}}
-
-For Rancher servers that will only provision Linux clusters, these are the steps to populate your private registry.
-
-A. Find the required assets for your Rancher version <br>
-B. Collect all the required images <br>
-C. Save the images to your workstation <br>
-D. Populate the private registry
-
-### Prerequisites
-
-These steps expect you to use a Linux workstation that has internet access, access to your private registry, and at least 20 GB of disk space.
-
-If you will use ARM64 hosts, the registry must support manifests. As of April 2020, Amazon Elastic Container Registry does not support manifests.
-
-### A. Find the required assets for your Rancher version
-
-1. Browse to our [releases page](https://github.com/rancher/rancher/releases) and find the Rancher v2.x.x release that you want to install. Don't download releases marked `rc` or `Pre-release`, as they are not stable for production environments. Click **Assets*.*
-
-2. From the release's **Assets** section, download the following files:
-
-| Release File   | Description  |
-| ---------------- | -------------- |
-| `rancher-images.txt`     | This file contains a list of images needed to install Rancher, provision clusters and user Rancher tools. |
-| `rancher-save-images.sh` | This script pulls all the images in the `rancher-images.txt` from Docker Hub and saves all of the images as `rancher-images.tar.gz`. |
-| `rancher-load-images.sh` | This script loads images from the `rancher-images.tar.gz` file and pushes them to your private registry.   |
-
-### B. Collect all the required images (For Kubernetes Installs using Rancher Generated Self-Signed Certificate)
-
-In a Kubernetes Install, if you elect to use the Rancher default self-signed TLS certificates, you must add the [`cert-manager`](https://hub.helm.sh/charts/jetstack/cert-manager) image to `rancher-images.txt` as well. You skip this step if you are using you using your own certificates.
-
-1.  Fetch the latest `cert-manager` Helm chart and parse the template for image details:
-
-    > **Note:** Recent changes to cert-manager require an upgrade. If you are upgrading Rancher and using a version of cert-manager older than v0.12.0, please see our [upgrade documentation]({{<baseurl>}}/rancher/v2.x/en/installation/options/upgrading-cert-manager/).
-
-    ```plain
-    helm repo add jetstack https://charts.jetstack.io
-    helm repo update
-    helm fetch jetstack/cert-manager --version v0.12.0
-    helm template ./cert-manager-<version>.tgz | grep -oP '(?<=image: ").*(?=")' >> ./rancher-images.txt
-    ```
-
-2.  Sort and unique the images list to remove any overlap between the sources:
-
-    ```plain
-    sort -u rancher-images.txt -o rancher-images.txt
-    ```
-
-### C. Save the images to your workstation
-
-1. Make `rancher-save-images.sh` an executable:
-   ```
-   chmod +x rancher-save-images.sh
-   ```
-
-1. Run `rancher-save-images.sh` with the `rancher-images.txt` image list to create a tarball of all the required images:
-   ```plain
-   ./rancher-save-images.sh --image-list ./rancher-images.txt
-   ```
-   **Result:** Docker begins pulling the images used for an air gap install. Be patient. This process takes a few minutes. When the process completes, your current directory will output a tarball named `rancher-images.tar.gz`. Check that the output is in the directory.
-
-### D. Populate the private registry
-
-Move the images in the `rancher-images.tar.gz` to your private registry using the scripts to load the images. The `rancher-images.txt` is expected to be on the workstation in the same directory that you are running the `rancher-load-images.sh` script.
-
-1.  Log into your private registry if required:
-    ```plain
-    docker login <REGISTRY.YOURDOMAIN.COM:PORT>
-    ```
-1.  Make `rancher-load-images.sh` an executable:
-    ```
-    chmod +x rancher-load-images.sh
-    ```
-
-1.  Use `rancher-load-images.sh` to extract, tag and push `rancher-images.txt` and `rancher-images.tar.gz` to your private registry:
-    ```plain
-     ./rancher-load-images.sh --image-list ./rancher-images.txt --registry <REGISTRY.YOURDOMAIN.COM:PORT>
-    ```
-{{% /tab %}}
-{{% tab "Linux and Windows Clusters" %}}
-
-_Available as of v2.3.0_
-
-For Rancher servers that will provision Linux and Windows clusters, there are distinctive steps to populate your private registry for the Windows images and the Linux images. Since a Windows cluster is a mix of Linux and Windows nodes, the Linux images pushed into the private registry are manifests.
-
-### Windows Steps
-
-The Windows images need to be collected and pushed from a Windows server workstation.
-
-A. Find the required assets for your Rancher version <br>
-B. Save the images to your Windows Server workstation <br>
-C. Prepare the Docker daemon <br>
-D. Populate the private registry
-
-{{% accordion label="Collecting and Populating Windows Images into the Private Registry"%}}
-
-### Prerequisites
-
-These steps expect you to use a Windows Server 1809 workstation that has internet access, access to your private registry, and at least 50 GB of disk space.
-
-The workstation must have Docker 18.02+ in order to support manifests, which are required when provisioning Windows clusters.
-
-Your registry must support manifests. As of April 2020, Amazon Elastic Container Registry does not support manifests.
-
-### A. Find the required assets for your Rancher version
-
-1. Browse to our [releases page](https://github.com/rancher/rancher/releases) and find the Rancher v2.x.x release that you want to install. Don't download releases marked `rc` or `Pre-release`, as they are not stable for production environments.
-
-2. From the release's "Assets" section, download the following files:
-
-| Release File         | Description      |
-|------------------------|-------------------|
-| `rancher-windows-images.txt` | This file contains a list of Windows images needed to provision Windows clusters.         |
-| `rancher-save-images.ps1`    | This script pulls all the images in the `rancher-windows-images.txt` from Docker Hub and saves all of the images as `rancher-windows-images.tar.gz`. |
-| `rancher-load-images.ps1`    | This script loads the images from the `rancher-windows-images.tar.gz` file and pushes them to your private registry.  |
-
-### B. Save the images to your Windows Server workstation
-
-1. Using `powershell`, go to the directory that has the files that were downloaded in the previous step.
-
-1. Run `rancher-save-images.ps1` to create a tarball of all the required images:
-
-   ```plain
-   ./rancher-save-images.ps1
-   ```
-
-   **Step Result:** Docker begins pulling the images used for an air gap install. Be patient. This process takes a few minutes. When the process completes, your current directory will output a tarball named `rancher-windows-images.tar.gz`. Check that the output is in the directory.
-
-### C. Prepare the Docker daemon
-
-Append your private registry address to the `allow-nondistributable-artifacts` config field in the Docker daemon (`C:\ProgramData\Docker\config\daemon.json`). Since the base image of Windows images are maintained by the `mcr.microsoft.com` registry, this step is required as the layers in the Microsoft registry are missing from Docker Hub and need to be pulled into the private registry.
-
-   ```
-   {
-     ...
-     "allow-nondistributable-artifacts": [
-       ...
-       "<REGISTRY.YOURDOMAIN.COM:PORT>"
-     ]
-     ...
-   }
-   ```
-
-### D. Populate the private registry
-
-Move the images in the `rancher-windows-images.tar.gz` to your private registry using the scripts to load the images. The `rancher-windows-images.txt` is expected to be on the workstation in the same directory that you are running the `rancher-load-images.ps1` script.
-
-1. Using `powershell`, log into your private registry if required:
-   ```plain
-   docker login <REGISTRY.YOURDOMAIN.COM:PORT>
-   ```
-
-1. Using `powershell`, use `rancher-load-images.ps1` to extract, tag and push the images from `rancher-images.tar.gz` to your private registry:
-   ```plain
-   ./rancher-load-images.ps1 --registry <REGISTRY.YOURDOMAIN.COM:PORT>
-   ```
-
-{{% /accordion %}}
-
-### Linux Steps
-
-The Linux images needs to be collected and pushed from a Linux host, but _must be done after_ populating the Windows images into the private registry. These step are different from the Linux only steps as the Linux images that are pushed will actually manifests that support Windows and Linux images.
-
-A. Find the required assets for your Rancher version <br>
-B. Collect all the required images <br>
-C. Save the images to your Linux workstation <br>
-D. Populate the private registry
-
-{{% accordion label="Collecting and Populating Linux Images into the Private Registry" %}}
-
-### Prerequisites
-
-You must populate the private registry with the Windows images before populating the private registry with Linux images. If you have already populated the registry with Linux images, you will need to follow these instructions again as they will publish manifests that support Windows and Linux images.
-
-These steps expect you to use a Linux workstation that has internet access, access to your private registry, and at least 20 GB of disk space.
-
-The workstation must have Docker 18.02+ in order to support manifests, which are required when provisioning Windows clusters.
-
-### A. Find the required assets for your Rancher version
-
-1. Browse to our [releases page](https://github.com/rancher/rancher/releases) and find the Rancher v2.x.x release that you want to install. Don't download releases marked `rc` or `Pre-release`, as they are not stable for production environments.
-
-2. From the release's **Assets** section, download the following files, which are required to install Rancher in an air gap environment:
-
-| Release File                 | Description |
-|----------------------------|------|
-| `rancher-images.txt`         | This file contains a list of images needed to install Rancher, provision clusters and user Rancher tools.                            |
-| `rancher-windows-images.txt` | This file contains a list of images needed to provision Windows clusters.                                                            |
-| `rancher-save-images.sh`     | This script pulls all the images in the `rancher-images.txt` from Docker Hub and saves all of the images as `rancher-images.tar.gz`. |
-| `rancher-load-images.sh`     | This script loads images from the `rancher-images.tar.gz` file and pushes them to your private registry.                             |
-
-### B. Collect all the required images
-
-**For Kubernetes Installs using Rancher Generated Self-Signed Certificate:** In a Kubernetes Install, if you elect to use the Rancher default self-signed TLS certificates, you must add the [`cert-manager`](https://hub.helm.sh/charts/jetstack/cert-manager) image to `rancher-images.txt` as well. You skip this step if you are using you using your own certificates.
-
-   1. Fetch the latest `cert-manager` Helm chart and parse the template for image details:
-      > **Note:** Recent changes to cert-manager require an upgrade. If you are upgrading Rancher and using a version of cert-manager older than v0.12.0, please see our [upgrade documentation]({{<baseurl>}}/rancher/v2.x/en/installation/options/upgrading-cert-manager/).
-      ```plain
-      helm repo add jetstack https://charts.jetstack.io
-      helm repo update
-      helm fetch jetstack/cert-manager --version v0.12.0
-      helm template ./cert-manager-<version>.tgz | grep -oP '(?<=image: ").*(?=")' >> ./rancher-images.txt
-      ```
-
-   2. Sort and unique the images list to remove any overlap between the sources:
-      ```plain
-      sort -u rancher-images.txt -o rancher-images.txt
-      ```
-
-### C. Save the images to your workstation
-
-1. Make `rancher-save-images.sh` an executable:
-   ```
-   chmod +x rancher-save-images.sh
-   ```
-
-1. Run `rancher-save-images.sh` with the `rancher-images.txt` image list to create a tarball of all the required images:
-   ```plain
-   ./rancher-save-images.sh --image-list ./rancher-images.txt
-   ```
-
-   **Result:** Docker begins pulling the images used for an air gap install. Be patient. This process takes a few minutes. When the process completes, your current directory will output a tarball named `rancher-images.tar.gz`. Check that the output is in the directory.
-
-### D. Populate the private registry
-
-Move the images in the `rancher-images.tar.gz` to your private registry using the `rancher-load-images.sh script` to load the images. The `rancher-images.txt` / `rancher-windows-images.txt` image list is expected to be on the workstation in the same directory that you are running the `rancher-load-images.sh` script.
-
-1. Log into your private registry if required:
-   ```plain
-   docker login <REGISTRY.YOURDOMAIN.COM:PORT>
-   ```
-
-1. Make `rancher-load-images.sh` an executable:
-   ```
-   chmod +x rancher-load-images.sh
-   ```
-
-1. Use `rancher-load-images.sh` to extract, tag and push the images from `rancher-images.tar.gz` to your private registry:
-   ```plain
-   ./rancher-load-images.sh --image-list ./rancher-images.txt \
-     --windows-image-list ./rancher-windows-images.txt \
-     --registry <REGISTRY.YOURDOMAIN.COM:PORT>
-   ```
-
-{{% /accordion %}}
-
-{{% /tab %}}
-{{% /tabs %}}
-
-### [Next: Kubernetes Installs - Launch a Kubernetes Cluster with RKE]({{<baseurl>}}/rancher/v2.x/en/installation/other-installation-methods/air-gap/launch-kubernetes/)
-
-### [Next: Docker Installs - Install Rancher]({{<baseurl>}}/rancher/v2.x/en/installation/other-installation-methods/air-gap/install-rancher/)
@@ -1,105 +0,0 @@
---
-title: '1. Prepare your Node(s)'
-weight: 100
-aliases:
-  - /rancher/v2.x/en/installation/air-gap-high-availability/provision-hosts
-  - /rancher/v2.x/en/installation/air-gap-single-node/provision-host
---
-
-This section is about how to prepare your node(s) to install Rancher for your air gapped environment. An air gapped environment could be where Rancher server will be installed offline, behind a firewall, or behind a proxy. There are _tabs_ for either a high availability (recommended) or a Docker installation.
-
-# Prerequisites
-
-{{% tabs %}}
-{{% tab "Kubernetes Install (Recommended)" %}}
-
-### OS, Docker, Hardware, and Networking
-
-Make sure that your node(s) fulfill the general [installation requirements.]({{<baseurl>}}/rancher/v2.x/en/installation/requirements/)
-
-### Private Registry
-
-Rancher supports air gap installs using a private registry. You must have your own private registry or other means of distributing Docker images to your machines.
-
-If you need help with creating a private registry, please refer to the [Docker documentation](https://docs.docker.com/registry/).
-
-### CLI Tools
-
-The following CLI tools are required for the Kubernetes Install. Make sure these tools are installed on your workstation and available in your `$PATH`.
-
- [kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/#install-kubectl) - Kubernetes command-line tool.
- [rke]({{<baseurl>}}/rke/latest/en/installation/) - Rancher Kubernetes Engine, cli for building Kubernetes clusters.
- [helm](https://docs.helm.sh/using_helm/#installing-helm) - Package management for Kubernetes. Refer to the [Helm version requirements]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm-version) to choose a version of Helm to install Rancher.
-
-{{% /tab %}}
-{{% tab "Docker Install" %}}
-
-### OS, Docker, Hardware, and Networking
-
-Make sure that your node(s) fulfill the general [installation requirements.]({{<baseurl>}}/rancher/v2.x/en/installation/requirements/)
-
-### Private Registry
-
-Rancher supports air gap installs using a private registry. You must have your own private registry or other means of distributing Docker images to your machines.
-
-If you need help with creating a private registry, please refer to the [Docker documentation](https://docs.docker.com/registry/).
-{{% /tab %}}
-{{% /tabs %}}
-
-# Set up Infrastructure
-
-{{% tabs %}}
-{{% tab "Kubernetes Install (Recommended)" %}}
-
-Rancher recommends installing Rancher on a Kubernetes cluster. A highly available Kubernetes install is comprised of three nodes running the Rancher server components on a Kubernetes cluster. The persistence layer (etcd) is also replicated on these three nodes, providing redundancy and data duplication in case one of the nodes fails.
-
-### Recommended Architecture
-
- DNS for Rancher should resolve to a layer 4 load balancer
- The Load Balancer should forward port TCP/80 and TCP/443 to all 3 nodes in the Kubernetes cluster.
- The Ingress controller will redirect HTTP to HTTPS and terminate SSL/TLS on port TCP/443.
- The Ingress controller will forward traffic to port TCP/80 on the pod in the Rancher deployment.
-
-<figcaption>Rancher installed on a Kubernetes cluster with layer 4 load balancer, depicting SSL termination at ingress controllers</figcaption>
-
-![Rancher HA]({{<baseurl>}}/img/rancher/ha/rancher2ha.svg)
-
-### A. Provision three air gapped Linux hosts according to our requirements
-
-These hosts will be disconnected from the internet, but require being able to connect with your private registry.
-
-View hardware and software requirements for each of your cluster nodes in [Requirements]({{<baseurl>}}/rancher/v2.x/en/installation/requirements).
-
-### B. Set up your Load Balancer
-
-When setting up the Kubernetes cluster that will run the Rancher server components, an Ingress controller pod will be deployed on each of your nodes. The Ingress controller pods are bound to ports TCP/80 and TCP/443 on the host network and are the entry point for HTTPS traffic to the Rancher server.
-
-You will need to configure a load balancer as a basic Layer 4 TCP forwarder to direct traffic to these ingress controller pods. The exact configuration will vary depending on your environment.
-
-> **Important:**
-> Only use this load balancer (i.e, the `local` cluster Ingress) to load balance the Rancher server. Sharing this Ingress with other applications may result in websocket errors to Rancher following Ingress configuration reloads for other apps.
-
-**Load Balancer Configuration Samples:**
-
- For an example showing how to set up an NGINX load balancer, refer to [this page.]({{<baseurl>}}/rancher/v2.x/en/installation/options/nginx)
- For an example showing how to set up an Amazon NLB load balancer, refer to [this page.]({{<baseurl>}}/rancher/v2.x/en/installation/options/nlb)
-
-{{% /tab %}}
-{{% tab "Docker Install" %}}
-
-The Docker installation is for Rancher users that are wanting to test out Rancher. Instead of running on a Kubernetes cluster, you install the Rancher server component on a single node using a `docker run` command. Since there is only one node and a single Docker container, if the node goes down, there is no copy of the etcd data available on other nodes and you will lose all the data of your Rancher server.
-
-> **Important:** If you install Rancher following the Docker installation guide, there is no upgrade path to transition your Docker installation to a Kubernetes Installation.
-
-Instead of running the Docker installation, you have the option to follow the Kubernetes Install guide, but only use one node to install Rancher. Afterwards, you can scale up the etcd nodes in your Kubernetes cluster to make it a Kubernetes Installation.
-
-### A. Provision a single, air gapped Linux host according to our Requirements
-
-These hosts will be disconnected from the internet, but require being able to connect with your private registry.
-
-View hardware and software requirements for each of your cluster nodes in [Requirements]({{<baseurl>}}/rancher/v2.x/en/installation/requirements).
-
-{{% /tab %}}
-{{% /tabs %}}
-
-### [Next: Collect and Publish Images to your Private Registry]({{<baseurl>}}/rancher/v2.x/en/installation/other-installation-methods/air-gap/populate-private-registry/)
@@ -1,160 +0,0 @@
---
-title: Template for an RKE Cluster with a Certificate Signed by Recognized CA and a Layer 4 Load Balancer
-weight: 3
---
-
-RKE uses a cluster.yml file to install and configure your Kubernetes cluster.
-
-The following template can be used for the cluster.yml if you have a setup with:
-
- Certificate signed by a recognized CA
- Layer 4 load balancer
- [NGINX Ingress controller](https://kubernetes.github.io/ingress-nginx/)
-
-> For more options, refer to [RKE Documentation: Config Options]({{<baseurl>}}/rke/latest/en/config-options/).
-
-```yaml
-nodes:
-  - address: <IP> # hostname or IP to access nodes
-    user: <USER> # root user (usually 'root')
-    role: [controlplane,etcd,worker] # K8s roles for node
-    ssh_key_path: <PEM_FILE> # path to PEM file
-  - address: <IP>
-    user: <USER>
-    role: [controlplane,etcd,worker]
-    ssh_key_path: <PEM_FILE>
-  - address: <IP>
-    user: <USER>
-    role: [controlplane,etcd,worker]
-    ssh_key_path: <PEM_FILE>
-
-services:
-  etcd:
-    snapshot: true
-    creation: 6h
-    retention: 24h
-
-addons: |-
-  ---
-  kind: Namespace
-  apiVersion: v1
-  metadata:
-    name: cattle-system
-  ---
-  kind: ServiceAccount
-  apiVersion: v1
-  metadata:
-    name: cattle-admin
-    namespace: cattle-system
-  ---
-  kind: ClusterRoleBinding
-  apiVersion: rbac.authorization.k8s.io/v1
-  metadata:
-    name: cattle-crb
-    namespace: cattle-system
-  subjects:
-  - kind: ServiceAccount
-    name: cattle-admin
-    namespace: cattle-system
-  roleRef:
-    kind: ClusterRole
-    name: cluster-admin
-    apiGroup: rbac.authorization.k8s.io
-  ---
-  apiVersion: v1
-  kind: Secret
-  metadata:
-    name: cattle-keys-ingress
-    namespace: cattle-system
-  type: Opaque
-  data:
-    tls.crt: <BASE64_CRT>  # ssl cert for ingress. If self-signed, must be signed by same CA as cattle server
-    tls.key: <BASE64_KEY>  # ssl key for ingress. If self-signed, must be signed by same CA as cattle server
-  ---
-  apiVersion: v1
-  kind: Service
-  metadata:
-    namespace: cattle-system
-    name: cattle-service
-    labels:
-      app: cattle
-  spec:
-    ports:
-    - port: 80
-      targetPort: 80
-      protocol: TCP
-      name: http
-    - port: 443
-      targetPort: 443
-      protocol: TCP
-      name: https
-    selector:
-      app: cattle
-  ---
-  apiVersion: extensions/v1beta1
-  kind: Ingress
-  metadata:
-    namespace: cattle-system
-    name: cattle-ingress-http
-    annotations:
-      nginx.ingress.kubernetes.io/proxy-connect-timeout: "30"
-      nginx.ingress.kubernetes.io/proxy-read-timeout: "1800"   # Max time in seconds for ws to remain shell window open
-      nginx.ingress.kubernetes.io/proxy-send-timeout: "1800"   # Max time in seconds for ws to remain shell window open
-  spec:
-    rules:
-    - host: <FQDN>  # FQDN to access cattle server
-      http:
-        paths:
-        - backend:
-            serviceName: cattle-service
-            servicePort: 80
-    tls:
-    - secretName: cattle-keys-ingress
-      hosts:
-      - <FQDN>      # FQDN to access cattle server
-  ---
-  kind: Deployment
-  apiVersion: extensions/v1beta1
-  metadata:
-    namespace: cattle-system
-    name: cattle
-  spec:
-    replicas: 1
-    template:
-      metadata:
-        labels:
-          app: cattle
-      spec:
-        serviceAccountName: cattle-admin
-        containers:
-        # Rancher install via RKE addons is only supported up to v2.0.8
-        - image: rancher/rancher:v2.0.8
-          args:
-          - --no-cacerts
-          imagePullPolicy: Always
-          name: cattle-server
-  #       env:
-  #       - name: HTTP_PROXY
-  #         value: "http://your_proxy_address:port"
-  #       - name: HTTPS_PROXY
-  #         value: "http://your_proxy_address:port"
-  #       - name: NO_PROXY
-  #         value: "localhost,127.0.0.1,0.0.0.0,10.43.0.0/16,your_network_ranges_that_dont_need_proxy_to_access"
-          livenessProbe:
-            httpGet:
-              path: /ping
-              port: 80
-            initialDelaySeconds: 60
-            periodSeconds: 60
-          readinessProbe:
-            httpGet:
-              path: /ping
-              port: 80
-            initialDelaySeconds: 20
-            periodSeconds: 10
-          ports:
-          - containerPort: 80
-            protocol: TCP
-          - containerPort: 443
-            protocol: TCP
-```
@@ -1,175 +0,0 @@
---
-title: Template for an RKE Cluster with a Self-signed Certificate and Layer 4 Load Balancer
-weight: 2
---
-RKE uses a cluster.yml file to install and configure your Kubernetes cluster.
-
-The following template can be used for the cluster.yml if you have a setup with:
-
- Self-signed SSL
- Layer 4 load balancer
- [NGINX Ingress controller](https://kubernetes.github.io/ingress-nginx/)
-
-> For more options, refer to [RKE Documentation: Config Options]({{<baseurl>}}/rke/latest/en/config-options/).
-
-```yaml
-nodes:
-  - address: <IP> # hostname or IP to access nodes
-    user: <USER> # root user (usually 'root')
-    role: [controlplane,etcd,worker] # K8s roles for node
-    ssh_key_path: <PEM_FILE> # path to PEM file
-  - address: <IP>
-    user: <USER>
-    role: [controlplane,etcd,worker]
-    ssh_key_path: <PEM_FILE>
-  - address: <IP>
-    user: <USER>
-    role: [controlplane,etcd,worker]
-    ssh_key_path: <PEM_FILE>
-
-services:
-  etcd:
-    snapshot: true
-    creation: 6h
-    retention: 24h
-
-addons: |-
-  ---
-  kind: Namespace
-  apiVersion: v1
-  metadata:
-    name: cattle-system
-  ---
-  kind: ServiceAccount
-  apiVersion: v1
-  metadata:
-    name: cattle-admin
-    namespace: cattle-system
-  ---
-  kind: ClusterRoleBinding
-  apiVersion: rbac.authorization.k8s.io/v1
-  metadata:
-    name: cattle-crb
-    namespace: cattle-system
-  subjects:
-  - kind: ServiceAccount
-    name: cattle-admin
-    namespace: cattle-system
-  roleRef:
-    kind: ClusterRole
-    name: cluster-admin
-    apiGroup: rbac.authorization.k8s.io
-  ---
-  apiVersion: v1
-  kind: Secret
-  metadata:
-    name: cattle-keys-ingress
-    namespace: cattle-system
-  type: Opaque
-  data:
-    tls.crt: <BASE64_CRT>  # ssl cert for ingress. If selfsigned, must be signed by same CA as cattle server
-    tls.key: <BASE64_KEY>  # ssl key for ingress. If selfsigned, must be signed by same CA as cattle server
-  ---
-  apiVersion: v1
-  kind: Secret
-  metadata:
-    name: cattle-keys-server
-    namespace: cattle-system
-  type: Opaque
-  data:
-    cacerts.pem: <BASE64_CA>  # CA cert used to sign cattle server cert and key
-  ---
-  apiVersion: v1
-  kind: Service
-  metadata:
-    namespace: cattle-system
-    name: cattle-service
-    labels:
-      app: cattle
-  spec:
-    ports:
-    - port: 80
-      targetPort: 80
-      protocol: TCP
-      name: http
-    - port: 443
-      targetPort: 443
-      protocol: TCP
-      name: https
-    selector:
-      app: cattle
-  ---
-  apiVersion: extensions/v1beta1
-  kind: Ingress
-  metadata:
-    namespace: cattle-system
-    name: cattle-ingress-http
-    annotations:
-      nginx.ingress.kubernetes.io/proxy-connect-timeout: "30"
-      nginx.ingress.kubernetes.io/proxy-read-timeout: "1800"   # Max time in seconds for ws to remain shell window open
-      nginx.ingress.kubernetes.io/proxy-send-timeout: "1800"   # Max time in seconds for ws to remain shell window open
-  spec:
-    rules:
-    - host: <FQDN>  # FQDN to access cattle server
-      http:
-        paths:
-        - backend:
-            serviceName: cattle-service
-            servicePort: 80
-    tls:
-    - secretName: cattle-keys-ingress
-      hosts:
-      - <FQDN>      # FQDN to access cattle server
-  ---
-  kind: Deployment
-  apiVersion: extensions/v1beta1
-  metadata:
-    namespace: cattle-system
-    name: cattle
-  spec:
-    replicas: 1
-    template:
-      metadata:
-        labels:
-          app: cattle
-      spec:
-        serviceAccountName: cattle-admin
-        containers:
-        # Rancher install via RKE addons is only supported up to v2.0.8
-        - image: rancher/rancher:v2.0.8
-          imagePullPolicy: Always
-          name: cattle-server
-  #       env:
-  #       - name: HTTP_PROXY
-  #         value: "http://your_proxy_address:port"
-  #       - name: HTTPS_PROXY
-  #         value: "http://your_proxy_address:port"
-  #       - name: NO_PROXY
-  #         value: "localhost,127.0.0.1,0.0.0.0,10.43.0.0/16,your_network_ranges_that_dont_need_proxy_to_access"
-          livenessProbe:
-            httpGet:
-              path: /ping
-              port: 80
-            initialDelaySeconds: 60
-            periodSeconds: 60
-          readinessProbe:
-            httpGet:
-              path: /ping
-              port: 80
-            initialDelaySeconds: 20
-            periodSeconds: 10
-          ports:
-          - containerPort: 80
-            protocol: TCP
-          - containerPort: 443
-            protocol: TCP
-          volumeMounts:
-          - mountPath: /etc/rancher/ssl
-            name: cattle-keys-volume
-            readOnly: true
-        volumes:
-        - name: cattle-keys-volume
-          secret:
-            defaultMode: 420
-            secretName: cattle-keys-server
-```
@@ -1,158 +0,0 @@
---
-title: Template for an RKE Cluster with a Self-signed Certificate and SSL Termination on Layer 7 Load Balancer
-weight: 3
---
-
-RKE uses a cluster.yml file to install and configure your Kubernetes cluster.
-
-This template is intended to be used for RKE add-on installs, which are only supported up to Rancher v2.0.8. Please use the Rancher Helm chart if you are installing a newer Rancher version. For details, see the [Kubernetes Install - Installation Outline]({{<baseurl>}}/rancher/v2.x/en/installation/k8s-install/#installation-outline).
-
-The following template can be used for the cluster.yml if you have a setup with:
-
- Layer 7 load balancer with self-signed SSL termination (HTTPS)
- [NGINX Ingress controller](https://kubernetes.github.io/ingress-nginx/) 
-
-> For more options, refer to [RKE Documentation: Config Options]({{<baseurl>}}/rke/latest/en/config-options/).
-
-```yaml
-nodes:
-  - address: <IP> # hostname or IP to access nodes
-    user: <USER> # root user (usually 'root')
-    role: [controlplane,etcd,worker] # K8s roles for node
-    ssh_key_path: <PEM_FILE> # path to PEM file
-  - address: <IP>
-    user: <USER>
-    role: [controlplane,etcd,worker]
-    ssh_key_path: <PEM_FILE>
-  - address: <IP>
-    user: <USER>
-    role: [controlplane,etcd,worker]
-    ssh_key_path: <PEM_FILE>
-
-services:
-  etcd:
-    snapshot: true
-    creation: 6h
-    retention: 24h
-
-addons: |-
-  ---
-  kind: Namespace
-  apiVersion: v1
-  metadata:
-    name: cattle-system
-  ---
-  kind: ServiceAccount
-  apiVersion: v1
-  metadata:
-    name: cattle-admin
-    namespace: cattle-system
-  ---
-  kind: ClusterRoleBinding
-  apiVersion: rbac.authorization.k8s.io/v1
-  metadata:
-    name: cattle-crb
-    namespace: cattle-system
-  subjects:
-  - kind: ServiceAccount
-    name: cattle-admin
-    namespace: cattle-system
-  roleRef:
-    kind: ClusterRole
-    name: cluster-admin
-    apiGroup: rbac.authorization.k8s.io
-  ---
-  apiVersion: v1
-  kind: Secret
-  metadata:
-    name: cattle-keys-server
-    namespace: cattle-system
-  type: Opaque
-  data:
-    cacerts.pem: <BASE64_CA>  # CA cert used to sign cattle server cert and key
-  ---
-  apiVersion: v1
-  kind: Service
-  metadata:
-    namespace: cattle-system
-    name: cattle-service
-    labels:
-      app: cattle
-  spec:
-    ports:
-    - port: 80
-      targetPort: 80
-      protocol: TCP
-      name: http
-    selector:
-      app: cattle
-  ---
-  apiVersion: extensions/v1beta1
-  kind: Ingress
-  metadata:
-    namespace: cattle-system
-    name: cattle-ingress-http
-    annotations:
-      nginx.ingress.kubernetes.io/proxy-connect-timeout: "30"
-      nginx.ingress.kubernetes.io/proxy-read-timeout: "1800"   # Max time in seconds for ws to remain shell window open
-      nginx.ingress.kubernetes.io/proxy-send-timeout: "1800"   # Max time in seconds for ws to remain shell window open
-      nginx.ingress.kubernetes.io/ssl-redirect: "false"        # Disable redirect to ssl
-  spec:
-    rules:
-    - host: <FQDN>
-      http:
-        paths:
-        - backend:
-            serviceName: cattle-service
-            servicePort: 80
-  ---
-  kind: Deployment
-  apiVersion: extensions/v1beta1
-  metadata:
-    namespace: cattle-system
-    name: cattle
-  spec:
-    replicas: 1
-    template:
-      metadata:
-        labels:
-          app: cattle
-      spec:
-        serviceAccountName: cattle-admin
-        containers:
-        # Rancher install via RKE addons is only supported up to v2.0.8
-        - image: rancher/rancher:v2.0.8
-          imagePullPolicy: Always
-          name: cattle-server
-  #       env:
-  #       - name: HTTP_PROXY
-  #         value: "http://your_proxy_address:port"
-  #       - name: HTTPS_PROXY
-  #         value: "http://your_proxy_address:port"
-  #       - name: NO_PROXY
-  #         value: "localhost,127.0.0.1,0.0.0.0,10.43.0.0/16,your_network_ranges_that_dont_need_proxy_to_access"
-          livenessProbe:
-            httpGet:
-              path: /ping
-              port: 80
-            initialDelaySeconds: 60
-            periodSeconds: 60
-          readinessProbe:
-            httpGet:
-              path: /ping
-              port: 80
-            initialDelaySeconds: 20
-            periodSeconds: 10
-          ports:
-          - containerPort: 80
-            protocol: TCP
-          volumeMounts:
-          - mountPath: /etc/rancher/ssl
-            name: cattle-keys-volume
-            readOnly: true
-        volumes:
-        - name: cattle-keys-volume
-          secret:
-            defaultMode: 420
-            secretName: cattle-keys-server
-```
@@ -1,142 +0,0 @@
---
-title: Template for an RKE Cluster with a Recognized CA Certificate and SSL Termination on Layer 7 Load Balancer
-weight: 4
---
-
-RKE uses a cluster.yml file to install and configure your Kubernetes cluster.
-
-This template is intended to be used for RKE add-on installs, which are only supported up to Rancher v2.0.8. Please use the Rancher Helm chart if you are installing a newer Rancher version. For details, see the [Kubernetes Install - Installation Outline]({{<baseurl>}}/rancher/v2.x/en/installation/k8s-install/#installation-outline).
-
-The following template can be used for the cluster.yml if you have a setup with:
-
- Layer 7 load balancer with SSL termination (HTTPS)
- [NGINX Ingress controller](https://kubernetes.github.io/ingress-nginx/) 
-
-> For more options, refer to [RKE Documentation: Config Options]({{<baseurl>}}/rke/latest/en/config-options/).
-
-```yaml
-nodes:
-  - address: <IP> # hostname or IP to access nodes
-    user: <USER> # root user (usually 'root')
-    role: [controlplane,etcd,worker] # K8s roles for node
-    ssh_key_path: <PEM_FILE> # path to PEM file
-  - address: <IP>
-    user: <USER>
-    role: [controlplane,etcd,worker]
-    ssh_key_path: <PEM_FILE>
-  - address: <IP>
-    user: <USER>
-    role: [controlplane,etcd,worker]
-    ssh_key_path: <PEM_FILE>
-
-services:
-  etcd:
-    snapshot: true
-    creation: 6h
-    retention: 24h
-
-addons: |-
-  ---
-  kind: Namespace
-  apiVersion: v1
-  metadata:
-    name: cattle-system
-  ---
-  kind: ServiceAccount
-  apiVersion: v1
-  metadata:
-    name: cattle-admin
-    namespace: cattle-system
-  ---
-  kind: ClusterRoleBinding
-  apiVersion: rbac.authorization.k8s.io/v1
-  metadata:
-    name: cattle-crb
-    namespace: cattle-system
-  subjects:
-  - kind: ServiceAccount
-    name: cattle-admin
-    namespace: cattle-system
-  roleRef:
-    kind: ClusterRole
-    name: cluster-admin
-    apiGroup: rbac.authorization.k8s.io
-  ---
-  apiVersion: v1
-  kind: Service
-  metadata:
-    namespace: cattle-system
-    name: cattle-service
-    labels:
-      app: cattle
-  spec:
-    ports:
-    - port: 80
-      targetPort: 80
-      protocol: TCP
-      name: http
-    selector:
-      app: cattle
-  ---
-  apiVersion: extensions/v1beta1
-  kind: Ingress
-  metadata:
-    namespace: cattle-system
-    name: cattle-ingress-http
-    annotations:
-      nginx.ingress.kubernetes.io/proxy-connect-timeout: "30"
-      nginx.ingress.kubernetes.io/proxy-read-timeout: "1800"   # Max time in seconds for ws to remain shell window open
-      nginx.ingress.kubernetes.io/proxy-send-timeout: "1800"   # Max time in seconds for ws to remain shell window open
-      nginx.ingress.kubernetes.io/ssl-redirect: "false"        # Disable redirect to ssl
-  spec:
-    rules:
-    - host: <FQDN>
-      http:
-        paths:
-        - backend:
-            serviceName: cattle-service
-            servicePort: 80
-  ---
-  kind: Deployment
-  apiVersion: extensions/v1beta1
-  metadata:
-    namespace: cattle-system
-    name: cattle
-  spec:
-    replicas: 1
-    template:
-      metadata:
-        labels:
-          app: cattle
-      spec:
-        serviceAccountName: cattle-admin
-        containers:
-        # Rancher install via RKE addons is only supported up to v2.0.8
-        - image: rancher/rancher:v2.0.8
-          args:
-          - --no-cacerts
-          imagePullPolicy: Always
-          name: cattle-server
-  #       env:
-  #       - name: HTTP_PROXY
-  #         value: "http://your_proxy_address:port"
-  #       - name: HTTPS_PROXY
-  #         value: "http://your_proxy_address:port"
-  #       - name: NO_PROXY
-  #         value: "localhost,127.0.0.1,0.0.0.0,10.43.0.0/16,your_network_ranges_that_dont_need_proxy_to_access"
-          livenessProbe:
-            httpGet:
-              path: /ping
-              port: 80
-            initialDelaySeconds: 60
-            periodSeconds: 60
-          readinessProbe:
-            httpGet:
-              path: /ping
-              port: 80
-            initialDelaySeconds: 20
-            periodSeconds: 10
-          ports:
-          - containerPort: 80
-            protocol: TCP
-```
@@ -1,8 +0,0 @@
---
-title: cluster.yml Templates
-weight: 1
---
-
-RKE uses a cluster.yml file to install and configure your Kubernetes cluster. This section provides templates that can be used to create the cluster.yml.
-
-> For more cluster.yml options, refer to the[RKE configuration reference.]({{<baseurl>}}/rke/latest/en/config-options/).
@@ -1,156 +0,0 @@
---
-title: Enabling Experimental Features
-weight: 8000
---
-
-_Available as of v2.3.0_
-
-Rancher includes some features that are experimental and disabled by default. You might want to enable these features, for example, if you decide that the benefits of using an [unsupported storage type]({{<baseurl>}}/rancher/v2.x/en/installation/options/feature-flags/enable-not-default-storage-drivers) outweighs the risk of using an untested feature. Feature flags were introduced to allow you to try these features that are not enabled by default.
-
-The features can be enabled in three ways:
-
- [Enable features when starting Rancher.](#enabling-features-when-starting-rancher) When installing Rancher with a CLI, you can use a feature flag to enable a feature by default.
- [Enable features from the Rancher UI](#enabling-features-with-the-rancher-ui) in Rancher v2.3.3+ by going to the **Settings** page.
- [Enable features with the Rancher API](#enabling-features-with-the-rancher-api) after installing Rancher.
-
-Each feature has two values:
-
- A default value, which can be configured with a flag or environment variable from the command line
- A set value, which can be configured with the Rancher API or UI
-
-If no value has been set, Rancher uses the default value.
-
-Because the API sets the actual value and the command line sets the default value, that means that if you enable or disable a feature with the API or UI, it will override any value set with the command line.
-
-For example, if you install Rancher, then set a feature flag to true with the Rancher API, then upgrade Rancher with a command that sets the feature flag to false, the default value will still be false, but the feature will still be enabled because it was set with the Rancher API. If you then deleted the set value (true) with the Rancher API, setting it to NULL, the default value (false) would take effect.
-
-> **Note:** As of v2.4.0, there are some feature flags that may require a restart of the Rancher server container. These features that require a restart are marked in the table of these docs and in the UI.
-
-The following is a list of the feature flags available in Rancher:
-
- `dashboard`: This feature enables the new experimental UI that has a new look and feel. The dashboard also leverages a new API in Rancher which allows the UI to access the default Kubernetes resources without any intervention from Rancher.
- `istio-virtual-service-ui`: This feature enables a [UI to create, read, update, and delete Istio virtual services and destination rules]({{<baseurl>}}/rancher/v2.x/en/installation/options/feature-flags/istio-virtual-service-ui), which are traffic management features of Istio.
- `proxy`: This feature enables Rancher to use a new simplified code base for the proxy, which can help enhance performance and security. The proxy feature is known to have issues with Helm deployments, which prevents any catalog applications to be deployed which includes Rancher's tools like monitoring, logging, Istio, etc.
- `unsupported-storage-drivers`: This feature [allows unsupported storage drivers.]({{<baseurl>}}/rancher/v2.x/en/installation/options/feature-flags/enable-not-default-storage-drivers) In other words, it enables types for storage providers and provisioners that are not enabled by default.
-
-The below table shows the availability and default value for feature flags in Rancher:
-
-| Feature Flag Name             | Default Value | Status       | Available as of | Rancher Restart Required? |
-| ----------------------------- | ------------- | ------------ | --------------- |---|
-| `dashboard` | `true` | Experimental | v2.4.0 | x |
-| `istio-virtual-service-ui`    | `false`       | Experimental | v2.3.0          | |
-| `istio-virtual-service-ui`    | `true`        | GA           | v2.3.2          | |
-| `proxy` | `false` | Experimental | v2.4.0 | |
-| `unsupported-storage-drivers` | `false`       | Experimental | v2.3.0          | |
-
-# Enabling Features when Starting Rancher
-
-When you install Rancher, enable the feature you want with a feature flag. The command is different depending on whether you are installing Rancher on a single node or if you are doing a Kubernetes Installation of Rancher.
-
-> **Note:** Values set from the Rancher API will override the value passed in through the command line.
-
-{{% tabs %}}
-{{% tab "Kubernetes Install" %}}
-When installing Rancher with a Helm chart, use the `--features` option. In the below example, two features are enabled by passing the feature flag names names in a comma separated list:
-
-```
-helm install rancher-latest/rancher \
-  --name rancher \
-  --namespace cattle-system \
-  --set hostname=rancher.my.org \
-  --set 'extraEnv[0].name=CATTLE_FEATURES' # Available as of v2.3.0
-  --set 'extraEnv[0].value=<FEATURE-FLAG-NAME-1>=true,<FEATURE-FLAG-NAME-2>=true' # Available as of v2.3.0
-```
-
-Note: If you are installing an alpha version, Helm requires adding the `--devel` option to the command.
-
-### Rendering the Helm Chart for Air Gap Installations
-
-For an air gap installation of Rancher, you need to add a Helm chart repository and render a Helm template before installing Rancher with Helm. For details, refer to the [air gap installation documentation.]({{<baseurl>}}/rancher/v2.x/en/installation/other-installation-methods/air-gap/install-rancher)
-
-Here is an example of a command for passing in the feature flag names when rendering the Helm template. In the below example, two features are enabled by passing the feature flag names in a comma separated list.
-
-The Helm 3 command is as follows:
-
-```
-helm template rancher ./rancher-<VERSION>.tgz --output-dir . \
-  --namespace cattle-system \
-  --set hostname=<RANCHER.YOURDOMAIN.COM> \
-  --set rancherImage=<REGISTRY.YOURDOMAIN.COM:PORT>/rancher/rancher \
-  --set ingress.tls.source=secret \
-  --set systemDefaultRegistry=<REGISTRY.YOURDOMAIN.COM:PORT> \ # Available as of v2.2.0, set a default private registry to be used in Rancher
-  --set useBundledSystemChart=true # Available as of v2.3.0, use the packaged Rancher system charts
-  --set 'extraEnv[0].name=CATTLE_FEATURES' # Available as of v2.3.0
-  --set 'extraEnv[0].value=<FEATURE-FLAG-NAME-1>=true,<FEATURE-FLAG-NAME-2>=true' # Available as of v2.3.0
-```
-
-The Helm 2 command is as follows:
-
-```
-helm template ./rancher-<VERSION>.tgz --output-dir . \
-  --name rancher \
-  --namespace cattle-system \
-  --set hostname=<RANCHER.YOURDOMAIN.COM> \
-  --set rancherImage=<REGISTRY.YOURDOMAIN.COM:PORT>/rancher/rancher \
-  --set ingress.tls.source=secret \
-  --set systemDefaultRegistry=<REGISTRY.YOURDOMAIN.COM:PORT> \ # Available as of v2.2.0, set a default private registry to be used in Rancher
-  --set useBundledSystemChart=true # Available as of v2.3.0, use the packaged Rancher system charts
-  --set 'extraEnv[0].name=CATTLE_FEATURES' # Available as of v2.3.0
-  --set 'extraEnv[0].value=<FEATURE-FLAG-NAME-1>=true,<FEATURE-FLAG-NAME-2>=true' # Available as of v2.3.0
-```
-
-{{% /tab %}}
-{{% tab "Docker Install" %}}
-When installing Rancher with Docker, use the `--features` option. In the below example, two features are enabled by passing the feature flag names in a comma separated list:
-
-```
-docker run -d -p 80:80 -p 443:443 \
-  --restart=unless-stopped \
-  rancher/rancher:rancher-latest \
-  --features=<FEATURE-FLAG-NAME-1>=true,<FEATURE-NAME-2>=true # Available as of v2.3.0
-```
-
-{{% /tab %}}
-{{% /tabs %}}
-
-# Enabling Features with the Rancher UI
-
-_Available as of Rancher v2.3.3_
-
-1. Go to the **Global** view and click **Settings.**
-1. Click the **Feature Flags** tab. You will see a list of experimental features.
-1. To enable a feature, go to the disabled feature you want to enable and click **&#8942; > Activate.**
-
-**Result:** The feature is enabled.
-
-### Disabling Features with the Rancher UI
-
-1. Go to the **Global** view and click **Settings.**
-1. Click the **Feature Flags** tab. You will see a list of experimental features.
-1. To disable a feature, go to the enabled feature you want to disable and click **&#8942; > Deactivate.**
-
-**Result:** The feature is disabled.
-
-# Enabling Features with the Rancher API
-
-1. Go to `<RANCHER-SERVER-URL>/v3/features`.
-1. In the `data` section, you will see an array containing all of the features that can be turned on with feature flags. The name of the feature is in the `id` field. Click the name of the feature you want to enable.
-1. In the upper left corner of the screen, under **Operations,** click **Edit.**
-1. In the **Value** drop-down menu, click **True.**
-1. Click **Show Request.**
-1. Click **Send Request.**
-1. Click **Close.**
-
-**Result:** The feature is enabled.
-
-### Disabling Features with the Rancher API
-
-1. Go to `<RANCHER-SERVER-URL>/v3/features`.
-1. In the `data` section, you will see an array containing all of the features that can be turned on with feature flags. The name of the feature is in the `id` field. Click the name of the feature you want to enable.
-1. In the upper left corner of the screen, under **Operations,** click **Edit.**
-1. In the **Value** drop-down menu, click **False.**
-1. Click **Show Request.**
-1. Click **Send Request.**
-1. Click **Close.**
-
-**Result:** The feature is disabled.
@@ -1,43 +0,0 @@
---
-title: Allow Unsupported Storage Drivers
-weight: 1
-aliases:
-  - /rancher/v2.x/en/admin-settings/feature-flags/enable-not-default-storage-drivers
---
-_Available as of v2.3.0_
-
-This feature allows you to use types for storage providers and provisioners that are not enabled by default.
-
-To enable or disable this feature, refer to the instructions on [the main page about enabling experimental features.]({{<baseurl>}}/rancher/v2.x/en/installation/options/feature-flags/)
-
-Environment Variable Key | Default Value | Description
---|---|---
- `unsupported-storage-drivers` | `false` | This feature enables types for storage providers and provisioners that are not enabled by default.
-
-### Types for Persistent Volume Plugins that are Enabled by Default
-Below is a list of storage types for persistent volume plugins that are enabled by default. When enabling this feature flag, any persistent volume plugins that are not on this list are considered experimental and unsupported:
-
-Name | Plugin
--------|----------
-Amazon EBS Disk |  `aws-ebs`
-AzureFile | `azure-file`
-AzureDisk | `azure-disk`
-Google Persistent Disk | `gce-pd`
-Longhorn | `flex-volume-longhorn`
-VMware vSphere Volume |  `vsphere-volume`
-Local | `local`
-Network File System | `nfs`
-hostPath | `host-path`
-
-### Types for StorageClass that are Enabled by Default
-Below is a list of storage types for a StorageClass that are enabled by default. When enabling this feature flag, any persistent volume plugins that are not on this list are considered experimental and unsupported:
-
-Name | Plugin
--------|--------
-Amazon EBS Disk |  `aws-ebs`
-AzureFile | `azure-file`
-AzureDisk | `azure-disk`
-Google Persistent Disk | `gce-pd`
-Longhorn | `flex-volume-longhorn`
-VMware vSphere Volume | `vsphere-volume`
-Local | `local`
@@ -1,34 +0,0 @@
---
-title: UI for Istio Virtual Services and Destination Rules
-weight: 2
-aliases:
-  - /rancher/v2.x/en/admin-settings/feature-flags/istio-virtual-service-ui
---
-_Available as of v2.3.0_
-
-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.
-
-> **Prerequisite:** Turning on this feature does not enable Istio. A cluster administrator needs to [enable Istio for the cluster]({{<baseurl>}}/rancher/v2.x/en/cluster-admin/tools/istio/setup) in order to use the feature.
-
-To enable or disable this feature, refer to the instructions on [the main page about enabling experimental features.]({{<baseurl>}}/rancher/v2.x/en/installation/options/feature-flags/)
-
-Environment Variable Key | Default Value | Status | Available as of
---|---|---|---
-`istio-virtual-service-ui` |`false` |  Experimental | v2.3.0
-`istio-virtual-service-ui` | `true` | GA                    | v2.3.2
-
-# About this Feature
-
-A central advantage of Istio's traffic management features is that they allow dynamic request routing, which is useful for canary deployments, blue/green deployments, or A/B testing.
-
-When enabled, this feature turns on a page that lets you configure some traffic management features of Istio using the Rancher UI. Without this feature, you need to use `kubectl` to manage traffic with Istio.
-
-The feature enables two UI tabs: one tab for **Virtual Services** and another for **Destination Rules.** 
-
- **Virtual services** intercept and direct traffic to your Kubernetes services, allowing you to direct percentages of traffic from a request to different services. You can use them to define a set of routing rules to apply when a host is addressed. For details, refer to the [Istio documentation.](https://istio.io/docs/reference/config/networking/v1alpha3/virtual-service/)
- **Destination rules** serve as the single source of truth about which service versions are available to receive traffic from virtual services. You can use these resources to define policies that apply to traffic that is intended for a service after routing has occurred. For details, refer to the [Istio documentation.](https://istio.io/docs/reference/config/networking/v1alpha3/destination-rule)
-
-To see these tabs,
-
-1. Go to the project view in Rancher and click **Resources > Istio.**
-1. You will see tabs for **Traffic Graph,** which has the Kiali network visualization integrated into the UI, and **Traffic Metrics,** which shows metrics for the success rate and request volume of traffic to your services, among other metrics. Next to these tabs, you should see the tabs for **Virtual Services** and **Destination Rules.**
@@ -1,58 +0,0 @@
---
-title: Kubernetes Installation Using Helm 2
-weight: 1
---
-
-> After Helm 3 was released, the Rancher installation instructions were updated to use Helm 3.
->
-> If you are using Helm 2, we recommend [migrating to Helm 3](https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/) because it is simpler to use and more secure than Helm 2.
->
-> This section provides a copy of the older high-availability Kubernetes Rancher installation instructions that used Helm 2, and it is intended to be used if upgrading to Helm 3 is not feasible.
-
-For production environments, we recommend installing Rancher in a high-availability configuration so that your user base can always access Rancher Server. When installed in a Kubernetes cluster, Rancher will integrate with the cluster's etcd database and take advantage of Kubernetes scheduling for high-availability.
-
-This procedure walks you through setting up a 3-node cluster with Rancher Kubernetes Engine (RKE) and installing the Rancher chart with the Helm package manager.
-
-> **Important:** The Rancher management server can only be run on an RKE-managed Kubernetes cluster. Use of Rancher on hosted Kubernetes or other providers is not supported.
-
-> **Important:** For the best performance, we recommend a dedicated Kubernetes cluster for the Rancher management server. Running user workloads on this cluster is not advised. After deploying Rancher, you can [create or import clusters]({{<baseurl>}}/rancher/v2.x/en/cluster-provisioning/#cluster-creation-in-rancher) for running your workloads.
-
-## Recommended Architecture
-
- DNS for Rancher should resolve to a Layer 4 load balancer (TCP)
- The Load Balancer should forward port TCP/80 and TCP/443 to all 3 nodes in the Kubernetes cluster.
- The Ingress controller will redirect HTTP to HTTPS and terminate SSL/TLS on port TCP/443.
- The Ingress controller will forward traffic to port TCP/80 on the pod in the Rancher deployment.
-
-<figcaption>Kubernetes Rancher install with layer 4 load balancer, depicting SSL termination at ingress controllers</figcaption>
-![High-availability Kubernetes Install]({{<baseurl>}}/img/rancher/ha/rancher2ha.svg)
-<sup>Kubernetes Rancher install with Layer 4 load balancer (TCP), depicting SSL termination at ingress controllers</sup>
-
-## Required Tools
-
-The following CLI tools are required for this install. Please make sure these tools are installed and available in your `$PATH`
-
- [kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/#install-kubectl) - Kubernetes command-line tool.
- [rke]({{<baseurl>}}/rke/latest/en/installation/) - Rancher Kubernetes Engine, cli for building Kubernetes clusters.
- [helm](https://docs.helm.sh/using_helm/#installing-helm) - Package management for Kubernetes. Refer to the [Helm version requirements]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm-version) to choose a version of Helm to install Rancher.
-
-## Installation Outline
-
- [Create Nodes and Load Balancer]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/create-nodes-lb/)
- [Install Kubernetes with RKE]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/kubernetes-rke/)
- [Initialize Helm (tiller)]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/helm-init/)
- [Install Rancher]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/helm-rancher/)
-
-## Additional Install Options
-
- [Migrating from a Kubernetes Install with an RKE Add-on]({{<baseurl>}}/rancher/v2.x/en/upgrades/upgrades/migrating-from-rke-add-on/)
-
-## Previous Methods
-
-[RKE add-on install]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/rke-add-on/)
-
-> **Important: RKE add-on install is only supported up to Rancher v2.0.8**
->
-> Please use the Rancher helm chart to install Rancher on a Kubernetes cluster. For details, see the [Kubernetes Install - Installation Outline]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/#installation-outline).
->
-> If you are currently using the RKE add-on install method, see [Migrating from a Kubernetes Install with an RKE Add-on]({{<baseurl>}}/rancher/v2.x/en/upgrades/upgrades/migrating-from-rke-add-on/) for details on how to move to using the Helm chart.
@@ -1,30 +0,0 @@
---
-title: "1. Create Nodes and Load Balancer"
-weight: 185
---
-
-Use your provider of choice to provision 3 nodes and a Load Balancer endpoint for your RKE install.
-
-> **Note:** These nodes must be in the same region/datacenter.  You may place these servers in separate availability zones.
-
-### Node Requirements
-
-View the supported operating systems and hardware/software/networking requirements for nodes running Rancher at [Node Requirements]({{<baseurl>}}/rancher/v2.x/en/installation/requirements).
-
-View the OS requirements for RKE at [RKE Requirements]({{<baseurl>}}/rke/latest/en/os/)
-
-### Load Balancer
-
-RKE will configure an Ingress controller pod, on each of your nodes. The Ingress controller pods are bound to ports TCP/80 and TCP/443 on the host network and are the entry point for HTTPS traffic to the Rancher server.
-
-Configure a load balancer as a basic Layer 4 TCP forwarder. The exact configuration will vary depending on your environment. 
-
->**Important:**
->Do not use this load balancer (i.e, the `local` cluster Ingress) to load balance applications other than Rancher following installation. Sharing this Ingress with other applications may result in websocket errors to Rancher following Ingress configuration reloads for other apps. We recommend dedicating the `local` cluster to Rancher and no other applications.
-
-#### Examples
-
-* [Nginx]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/create-nodes-lb/nginx/)
-* [Amazon NLB]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/create-nodes-lb/nlb/)
-
-### [Next: Install Kubernetes with RKE]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/kubernetes-rke/)
@@ -1,79 +0,0 @@
---
-title: NGINX
-weight: 270
---
-NGINX will be configured as Layer 4 load balancer (TCP) that forwards connections to one of your Rancher nodes.
-
->**Note:**
-> In this configuration, the load balancer is positioned in front of your nodes. The load balancer can be any host capable of running NGINX.
->
-> One caveat: do not use one of your Rancher nodes as the load balancer.
-
-## Install NGINX
-
-Start by installing NGINX on the node you want to use as a load balancer. NGINX has packages available for all known operating systems. The versions tested are `1.14` and `1.15`. For help installing NGINX, refer to their [install documentation](https://www.nginx.com/resources/wiki/start/topics/tutorials/install/).
-
-The `stream` module is required, which is present when using the official NGINX packages. Please refer to your OS documentation on how to install and enable the NGINX `stream` module on your operating system.
-
-## Create NGINX Configuration
-
-After installing NGINX, you need to update the NGINX configuration file, `nginx.conf`, with the IP addresses for your nodes.
-
-1. Copy and paste the code sample below into your favorite text editor. Save it as `nginx.conf`.
-
-2. From `nginx.conf`, replace both occurrences (port 80 and port 443) of `<IP_NODE_1>`, `<IP_NODE_2>`, and `<IP_NODE_3>` with the IPs of your [nodes]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/create-nodes-lb/).
-
-    >**Note:** See [NGINX Documentation: TCP and UDP Load Balancing](https://docs.nginx.com/nginx/admin-guide/load-balancer/tcp-udp-load-balancer/) for all configuration options.
-
-    <figcaption>Example NGINX config</figcaption>
-    ```
-    worker_processes 4;
-    worker_rlimit_nofile 40000;
-
-    events {
-        worker_connections 8192;
-    }
-
-    stream {
-        upstream rancher_servers_http {
-            least_conn;
-            server <IP_NODE_1>:80 max_fails=3 fail_timeout=5s;
-            server <IP_NODE_2>:80 max_fails=3 fail_timeout=5s;
-            server <IP_NODE_3>:80 max_fails=3 fail_timeout=5s;
-        }
-        server {
-            listen     80;
-            proxy_pass rancher_servers_http;
-        }
-
-        upstream rancher_servers_https {
-            least_conn;
-            server <IP_NODE_1>:443 max_fails=3 fail_timeout=5s;
-            server <IP_NODE_2>:443 max_fails=3 fail_timeout=5s;
-            server <IP_NODE_3>:443 max_fails=3 fail_timeout=5s;
-        }
-        server {
-            listen     443;
-            proxy_pass rancher_servers_https;
-        }
-    }
-    ```
-
-3. Save `nginx.conf` to your load balancer at the following path: `/etc/nginx/nginx.conf`.
-
-4. Load the updates to your NGINX configuration by running the following command:
-
-    ```
-    # nginx -s reload
-    ```
-
-## Option - Run NGINX as Docker container
-
-Instead of installing NGINX as a package on the operating system, you can rather run it as a Docker container. Save the edited **Example NGINX config** as `/etc/nginx.conf` and run the following command to launch the NGINX container:
-
-```
-docker run -d --restart=unless-stopped \
-  -p 80:80 -p 443:443 \
-  -v /etc/nginx.conf:/etc/nginx/nginx.conf \
-  nginx:1.14
-```
@@ -1,175 +0,0 @@
---
-title: Amazon NLB
-weight: 277
---
-## Objectives
-
-Configuring an Amazon NLB is a multistage process. We've broken it down into multiple tasks so that it's easy to follow.
-
-1. [Create Target Groups](#create-target-groups)
-
-	Begin by creating two target groups for the **TCP** protocol, one regarding TCP port 443 and one regarding TCP port 80 (providing redirect to TCP port 443). You'll add your Linux nodes to these groups.
-
-2. [Register Targets](#register-targets)
-
-	Add your Linux nodes to the target groups.
-
-3. [Create Your NLB](#create-your-nlb)
-
-	Use Amazon's Wizard to create an Network Load Balancer. As part of this process, you'll add the target groups you created in **1. Create Target Groups**.
-
-> **Note:** Rancher only supports using the Amazon NLB when terminating traffic in `tcp` mode for port 443 rather than `tls` mode. This is due to the fact that the NLB does not inject the correct headers into requests when terminated at the NLB. This means that if you want to use certificates managed by the Amazon Certificate Manager (ACM), you should use an ELB or ALB.
-
-## Create Target Groups
-
-Your first NLB configuration step is to create two target groups. Technically, only port 443 is needed to access Rancher, but its convenient to add a listener for port 80 which will be redirected to port 443 automatically. The NGINX ingress controller on the nodes will make sure that port 80 gets redirected to port 443.
-
-Log into the [Amazon AWS Console](https://console.aws.amazon.com/ec2/) to get started, make sure to select the **Region** where your EC2 instances (Linux nodes) are created.
-
-The Target Groups configuration resides in the **Load Balancing** section of the **EC2** service. Select **Services** and choose **EC2**, find the section **Load Balancing** and open **Target Groups**.
-
-{{< img "/img/rancher/ha/nlb/ec2-loadbalancing.png" "EC2 Load Balancing section">}}
-
-Click **Create target group** to create the first target group, regarding TCP port 443.
-
-### Target Group (TCP port 443)
-
-Configure the first target group according to the table below. Screenshots of the configuration are shown just below the table.
-
-Option                                | Setting
--------------------------------------|------------------------------------
-Target Group Name                     | `rancher-tcp-443`
-Protocol                              | `TCP`
-Port                                  | `443`
-Target type                           | `instance`
-VPC                                   | Choose your VPC
-Protocol<br/>(Health Check)           | `HTTP`
-Path<br/>(Health Check)               | `/healthz`
-Port (Advanced health check)          | `override`,`80`
-Healthy threshold (Advanced health)   | `3`
-Unhealthy threshold (Advanced)        | `3`
-Timeout (Advanced)                    | `6 seconds`
-Interval (Advanced)                   | `10 second`
-Success codes                         | `200-399`
-
-<hr>
-**Screenshot Target group TCP port 443 settings**<br/>
-{{< img "/img/rancher/ha/nlb/create-targetgroup-443.png" "Target group 443">}}
-
-<hr>
-**Screenshot Target group TCP port 443 Advanced settings**<br/>
-{{< img "/img/rancher/ha/nlb/create-targetgroup-443-advanced.png" "Target group 443 Advanced">}}
-
-<hr>
-
-Click **Create target group** to create the second target group, regarding TCP port 80.
-
-### Target Group (TCP port 80)
-
-Configure the second target group according to the table below. Screenshots of the configuration are shown just below the table.
-
-Option                                | Setting
--------------------------------------|------------------------------------
-Target Group Name                     | `rancher-tcp-80`
-Protocol                              | `TCP`
-Port                                  | `80`
-Target type                           | `instance`
-VPC                                   | Choose your VPC
-Protocol<br/>(Health Check)           | `HTTP`
-Path<br/>(Health Check)               | `/healthz`
-Port (Advanced health check)          | `traffic port`
-Healthy threshold (Advanced health)   | `3`
-Unhealthy threshold (Advanced)        | `3`
-Timeout (Advanced)                    | `6 seconds`
-Interval (Advanced)                   | `10 second`
-Success codes                         | `200-399`
-
-<hr>
-**Screenshot Target group TCP port 80 settings**<br/>
-{{< img "/img/rancher/ha/nlb/create-targetgroup-80.png" "Target group 80">}}
-
-<hr>
-**Screenshot Target group TCP port 80 Advanced settings**<br/>
-{{< img "/img/rancher/ha/nlb/create-targetgroup-80-advanced.png" "Target group 80 Advanced">}}
-
-<hr>
-
-## Register Targets
-
-Next, add your Linux nodes to both target groups.
-
-Select the target group named **rancher-tcp-443**, click the tab **Targets** and choose **Edit**.
-
-{{< img "/img/rancher/ha/nlb/edit-targetgroup-443.png" "Edit target group 443">}}
-
-Select the instances (Linux nodes) you want to add, and click **Add to registered**.
-
-<hr>
-**Screenshot Add targets to target group TCP port 443**<br/>
-
-{{< img "/img/rancher/ha/nlb/add-targets-targetgroup-443.png" "Add targets to target group 443">}}
-
-<hr>
-**Screenshot Added targets to target group TCP port 443**<br/>
-
-{{< img "/img/rancher/ha/nlb/added-targets-targetgroup-443.png" "Added targets to target group 443">}}
-
-When the instances are added, click **Save** on the bottom right of the screen.
-
-Repeat those steps, replacing **rancher-tcp-443** with **rancher-tcp-80**. The same instances need to be added as targets to this target group.
-
-## Create Your NLB
-
-Use Amazon's Wizard to create an Network Load Balancer. As part of this process, you'll add the target groups you created in [Create Target Groups](#create-target-groups).
-
-1. From your web browser, navigate to the [Amazon EC2 Console](https://console.aws.amazon.com/ec2/).
-
-2. From the navigation pane, choose **LOAD BALANCING** > **Load Balancers**.
-
-3. Click **Create Load Balancer**.
-
-4. Choose **Network Load Balancer** and click **Create**.
-
-5. Complete the **Step 1: Configure Load Balancer** form.
-	- **Basic Configuration**
-
-	   - Name: `rancher`
-	   - Scheme: `internal` or `internet-facing`
-	   
-	     The Scheme that you choose for your NLB is dependent on the configuration of your instances/VPC. If your instances do not have public IPs associated with them, or you will only be accessing Rancher internally, you should set your NLB Scheme to `internal` rather than `internet-facing`. 
-	- **Listeners**
-
-		Add the **Load Balancer Protocols** and **Load Balancer Ports** below.
-		- `TCP`: `443`
-
-	- **Availability Zones**
-
-	   - Select Your **VPC** and **Availability Zones**.
-
-6. Complete the **Step 2: Configure Routing** form.
-
-	- From the **Target Group** drop-down, choose **Existing target group**.
-
-	- From the **Name** drop-down, choose `rancher-tcp-443`.
-
-	- Open **Advanced health check settings**, and configure **Interval** to `10 seconds`.
-
-7. Complete **Step 3: Register Targets**. Since you registered your targets earlier, all you have to do is click **Next: Review**.
-
-8. Complete **Step 4: Review**. Look over the load balancer details and click **Create** when you're satisfied.
-
-9. After AWS creates the NLB, click **Close**.
-
-## Add listener to NLB for TCP port 80
-
-1. Select your newly created NLB and select the **Listeners** tab.
-
-2. Click **Add listener**.
-
-3. Use `TCP`:`80` as **Protocol** : **Port**
-
-4. Click **Add action** and choose **Forward to...**
-
-5. From the **Forward to** drop-down, choose `rancher-tcp-80`.
-
-6. Click **Save** in the top right of the screen.
@@ -1,66 +0,0 @@
---
-title: "Initialize Helm: Install the Tiller Service"
-description: "With Helm, you can create configurable deployments instead of using static files. In order to use Helm, the Tiller service needs to be installed on your cluster."
-weight: 195
---
-
-Helm is the package management tool of choice for Kubernetes. Helm "charts" provide templating syntax for Kubernetes YAML manifest documents. With Helm we can create configurable deployments instead of just using static files. For more information about creating your own catalog of deployments, check out the docs at [https://helm.sh/](https://helm.sh/). To be able to use Helm, the server-side component `tiller` needs to be installed on your cluster.
-
-For systems without direct internet access, see [Helm - Air Gap]({{<baseurl>}}/rancher/v2.x/en/installation/air-gap-installation/install-rancher/#helm) for install details.
-
-Refer to the [Helm version requirements]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm-version) to choose a version of Helm to install Rancher.
-
-> **Note:** The installation instructions assume you are using Helm 2. The instructions will be updated for Helm 3 soon. In the meantime, if you want to use Helm 3, refer to [these instructions.](https://github.com/ibrokethecloud/rancher-helm3)
-
-### Install Tiller on the Cluster
-
-> **Important:** Due to an issue with Helm v2.12.0 and cert-manager, please use Helm v2.12.1 or higher.
-
-Helm installs the `tiller` service on your cluster to manage charts. Since RKE enables RBAC by default we will need to use `kubectl` to create a `serviceaccount` and `clusterrolebinding` so `tiller` has permission to deploy to the cluster.
-
-* Create the `ServiceAccount` in the `kube-system` namespace.
-* Create the `ClusterRoleBinding` to give the `tiller` account access to the cluster.
-* Finally use `helm` to install the `tiller` service
-
-```plain
-kubectl -n kube-system create serviceaccount tiller
-
-kubectl create clusterrolebinding tiller \
-  --clusterrole=cluster-admin \
-  --serviceaccount=kube-system:tiller
-
-helm init --service-account tiller
-
-# Users in China: You will need to specify a specific tiller-image in order to initialize tiller. 
-# The list of tiller image tags are available here: https://dev.aliyun.com/detail.html?spm=5176.1972343.2.18.ErFNgC&repoId=62085. 
-# When initializing tiller, you'll need to pass in --tiller-image
-
-helm init --service-account tiller \
--tiller-image registry.cn-hangzhou.aliyuncs.com/google_containers/tiller:<tag>
-```
-
-> **Note:** This`tiller`install has full cluster access, which should be acceptable if the cluster is dedicated to Rancher server. Check out the [helm docs](https://docs.helm.sh/using_helm/#role-based-access-control) for restricting `tiller` access to suit your security requirements.
-
-### Test your Tiller installation
-
-Run the following command to verify the installation of `tiller` on your cluster:
-
-```
-kubectl -n kube-system  rollout status deploy/tiller-deploy
-Waiting for deployment "tiller-deploy" rollout to finish: 0 of 1 updated replicas are available...
-deployment "tiller-deploy" successfully rolled out
-```
-
-And run the following command to validate Helm can talk to the `tiller` service:
-
-```
-helm version
-Client: &version.Version{SemVer:"v2.12.1", GitCommit:"02a47c7249b1fc6d8fd3b94e6b4babf9d818144e", GitTreeState:"clean"}
-Server: &version.Version{SemVer:"v2.12.1", GitCommit:"02a47c7249b1fc6d8fd3b94e6b4babf9d818144e", GitTreeState:"clean"}
-```
-
-### Issues or errors?
-
-See the [Troubleshooting]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/helm-init/troubleshooting/) page.
-
-### [Next: Install Rancher]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/helm-rancher/)
@@ -1,23 +0,0 @@
---
-title: Troubleshooting
-weight: 276
---
-
-### Helm commands show forbidden
-
-When Helm is initiated in the cluster without specifying the correct `ServiceAccount`, the command `helm init` will succeed but you won't be able to execute most of the other `helm` commands. The following error will be shown:
-
-```
-Error: configmaps is forbidden: User "system:serviceaccount:kube-system:default" cannot list configmaps in the namespace "kube-system"
-```
-
-To resolve this, the server component (`tiller`) needs to be removed and added with the correct `ServiceAccount`. You can use `helm reset --force` to remove the `tiller` from the cluster. Please check if it is removed using `helm version --server`.
-
-```
-helm reset --force
-Tiller (the Helm server-side component) has been uninstalled from your Kubernetes Cluster.
-helm version --server
-Error: could not find tiller
-```
-
-When you have confirmed that `tiller` has been removed, please follow the steps provided in [Initialize Helm (Install tiller)]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/helm-init/) to install `tiller` with the correct `ServiceAccount`.
@@ -1,218 +0,0 @@
---
-title: "4.  Install Rancher"
-weight: 200
---
-
-Rancher installation is managed using the Helm package manager for Kubernetes.  Use `helm` to install the prerequisite and charts to install Rancher.
-
-For systems without direct internet access, see [Air Gap: Kubernetes install]({{<baseurl>}}/rancher/v2.x/en/installation/air-gap-installation/install-rancher/).
-
-Refer to the [Helm version requirements]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm-version) to choose a version of Helm to install Rancher.
-
-> **Note:** The installation instructions assume you are using Helm 2. The instructions will be updated for Helm 3 soon. In the meantime, if you want to use Helm 3, refer to [these instructions.](https://github.com/ibrokethecloud/rancher-helm3)
-
-### Add the Helm Chart Repository
-
-Use `helm repo add` command to add the Helm chart repository that contains charts to install Rancher. For more information about the repository choices and which is best for your use case, see [Choosing a Version of Rancher]({{<baseurl>}}/rancher/v2.x/en/installation/options/server-tags/#helm-chart-repositories).
-
-{{< release-channel >}}
-
-```
-helm repo add rancher-<CHART_REPO> https://releases.rancher.com/server-charts/<CHART_REPO>
-```
-
-### Choose your SSL Configuration
-
-Rancher Server is designed to be secure by default and requires SSL/TLS configuration.
-
-There are three recommended options for the source of the certificate.
-
-> **Note:** If you want terminate SSL/TLS externally, see [TLS termination on an External Load Balancer]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/helm-rancher/chart-options/#external-tls-termination).
-
-| Configuration | Chart option | Description | Requires cert-manager |
-|-----|-----|-----|-----|
-| [Rancher Generated Certificates](#rancher-generated-certificates) | `ingress.tls.source=rancher` | Use certificates issued by Rancher's generated CA (self signed)<br/>This is the **default** | [yes](#optional-install-cert-manager) |
-| [Let’s Encrypt](#let-s-encrypt) | `ingress.tls.source=letsEncrypt` | Use [Let's Encrypt](https://letsencrypt.org/) to issue a certificate | [yes](#optional-install-cert-manager) |
-| [Certificates from Files](#certificates-from-files) | `ingress.tls.source=secret` | Use your own certificate files by creating Kubernetes Secret(s) | no |
-
-### Optional: Install cert-manager
-
-**Note:** cert-manager is only required for certificates issued by Rancher's generated CA (`ingress.tls.source=rancher`) and Let's Encrypt issued certificates (`ingress.tls.source=letsEncrypt`). You should skip this step if you are using your own certificate files (option `ingress.tls.source=secret`) or if you use [TLS termination on an External Load Balancer]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/helm-rancher/chart-options/#external-tls-termination).
-
-> **Important:**
-> Due to an issue with Helm v2.12.0 and cert-manager, please use Helm v2.12.1 or higher.
-
-> Recent changes to cert-manager require an upgrade. If you are upgrading Rancher and using a version of cert-manager older than v0.12.0, please see our [upgrade documentation]({{<baseurl>}}/rancher/v2.x/en/installation/options/upgrading-cert-manager/).
-
-Rancher relies on [cert-manager](https://github.com/jetstack/cert-manager) to issue certificates from Rancher's own generated CA or to request Let's Encrypt certificates.
-
-These instructions are adapted from the [official cert-manager documentation](https://docs.cert-manager.io/en/latest/getting-started/install/kubernetes.html#installing-with-helm).
-
-
-1. Install the CustomResourceDefinition resources separately
-    ```plain
-    kubectl apply -f https://raw.githubusercontent.com/jetstack/cert-manager/release-0.12/deploy/manifests/00-crds.yaml
-    ```
-
-1. Create the namespace for cert-manager
-    ```plain
-    kubectl create namespace cert-manager
-    ```
-
-1. Label the cert-manager namespace to disable resource validation
-    ```plain
-    kubectl label namespace cert-manager certmanager.k8s.io/disable-validation=true
-    ```
-
-1. Add the Jetstack Helm repository
-    ```plain
-    helm repo add jetstack https://charts.jetstack.io
-    ```
-
-1. Update your local Helm chart repository cache
-    ```plain
-    helm repo update
-    ```
-
-1. Install the cert-manager Helm chart
-    ```plain
-    helm install \
-      --name cert-manager \
-      --namespace cert-manager \
-      --version v0.12.0 \
-      jetstack/cert-manager
-    ```
-
-Once you’ve installed cert-manager, you can verify it is deployed correctly by checking the cert-manager namespace for running pods:
-
-```
-kubectl get pods --namespace cert-manager
-
-NAME                                            READY   STATUS      RESTARTS   AGE
-cert-manager-7cbdc48784-rpgnt                   1/1     Running     0          3m
-cert-manager-webhook-5b5dd6999-kst4x            1/1     Running     0          3m
-cert-manager-cainjector-3ba5cd2bcd-de332x       1/1     Running     0          3m
-```
-
-If the ‘webhook’ pod (2nd line) is in a ContainerCreating state, it may still be waiting for the Secret to be mounted into the pod. Wait a couple of minutes for this to happen but if you experience problems, please check the [troubleshooting](https://docs.cert-manager.io/en/latest/getting-started/troubleshooting.html) guide.
-
-<br/>
-
-#### Rancher Generated Certificates
-
-> **Note:** You need to have [cert-manager](#optional-install-cert-manager) installed before proceeding.
-
-The default is for Rancher to generate a CA and uses `cert-manager` to issue the certificate for access to the Rancher server interface. Because `rancher` is the default option for `ingress.tls.source`, we are not specifying `ingress.tls.source` when running the `helm install` command.
-
- Set the `hostname` to the DNS name you pointed at your load balancer.
- If you are installing an alpha version, Helm requires adding the `--devel` option to the command. 
-
-```
-helm install rancher-<CHART_REPO>/rancher \
-  --name rancher \
-  --namespace cattle-system \
-  --set hostname=rancher.my.org
-```
-
-Wait for Rancher to be rolled out:
-
-```
-kubectl -n cattle-system rollout status deploy/rancher
-Waiting for deployment "rancher" rollout to finish: 0 of 3 updated replicas are available...
-deployment "rancher" successfully rolled out
-```
-
-#### Let's Encrypt
-
-> **Note:** You need to have [cert-manager](#optional-install-cert-manager) installed before proceeding.
-
-This option uses `cert-manager` to automatically request and renew [Let's Encrypt](https://letsencrypt.org/) certificates. This is a free service that provides you with a valid certificate as Let's Encrypt is a trusted CA. This configuration uses HTTP validation (`HTTP-01`) so the load balancer must have a public DNS record and be accessible from the internet.
-
- Set `hostname` to the public DNS record, set `ingress.tls.source` to `letsEncrypt` and `letsEncrypt.email` to the email address used for communication about your certificate (for example, expiry notices)
- If you are installing an alpha version, Helm requires adding the `--devel` option to the command. 
-
-```
-helm install rancher-<CHART_REPO>/rancher \
-  --name rancher \
-  --namespace cattle-system \
-  --set hostname=rancher.my.org \
-  --set ingress.tls.source=letsEncrypt \
-  --set letsEncrypt.email=me@example.org
-```
-
-Wait for Rancher to be rolled out:
-
-```
-kubectl -n cattle-system rollout status deploy/rancher
-Waiting for deployment "rancher" rollout to finish: 0 of 3 updated replicas are available...
-deployment "rancher" successfully rolled out
-```
-
-#### Certificates from Files
-
-Create Kubernetes secrets from your own certificates for Rancher to use.
-
-
-> **Note:** The `Common Name` or a `Subject Alternative Names` entry in the server certificate must match the `hostname` option, or the ingress controller will fail to configure correctly. Although an entry in the `Subject Alternative Names` is technically required, having a matching `Common Name` maximizes compatibility with older browsers/applications. If you want to check if your certificates are correct, see [How do I check Common Name and Subject Alternative Names in my server certificate?]({{<baseurl>}}/rancher/v2.x/en/faq/technical/#how-do-i-check-common-name-and-subject-alternative-names-in-my-server-certificate)
-
- Set `hostname` and set `ingress.tls.source` to `secret`.
- If you are installing an alpha version, Helm requires adding the `--devel` option to the command. 
-
-```
-helm install rancher-<CHART_REPO>/rancher \
-  --name rancher \
-  --namespace cattle-system \
-  --set hostname=rancher.my.org \
-  --set ingress.tls.source=secret
-```
-
-If you are using a Private CA signed certificate , add `--set privateCA=true` to the command:
-
-```
-helm install rancher-<CHART_REPO>/rancher \
-  --name rancher \
-  --namespace cattle-system \
-  --set hostname=rancher.my.org \
-  --set ingress.tls.source=secret
-  --set privateCA=true
-```
-
-Now that Rancher is deployed, see [Adding TLS Secrets]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/helm-rancher/tls-secrets/) to publish the certificate files so Rancher and the ingress controller can use them.
-
-After adding the secrets, check if Rancher was rolled out successfully:
-
-```
-kubectl -n cattle-system rollout status deploy/rancher
-Waiting for deployment "rancher" rollout to finish: 0 of 3 updated replicas are available...
-deployment "rancher" successfully rolled out
-```
-
-If you see the following error: `error: deployment "rancher" exceeded its progress deadline`, you can check the status of the deployment by running the following command:
-
-```
-kubectl -n cattle-system get deploy rancher
-NAME      DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
-rancher   3         3         3            3           3m
-```
-
-It should show the same count for `DESIRED` and `AVAILABLE`.
-
-### Advanced Configurations
-
-The Rancher chart configuration has many options for customizing the install to suit your specific environment. Here are some common advanced scenarios.
-
-* [HTTP Proxy]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/helm-rancher/chart-options/#http-proxy)
-* [Private Docker Image Registry]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/helm-rancher/chart-options/#private-registry-and-air-gap-installs)
-* [TLS Termination on an External Load Balancer]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/helm-rancher/chart-options/#external-tls-termination)
-
-See the [Chart Options]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/helm-rancher/chart-options/) for the full list of options.
-
-### Save your options
-
-Make sure you save the `--set` options you used. You will need to use the same options when you upgrade Rancher to new versions with Helm.
-
-### Finishing Up
-
-That's it you should have a functional Rancher server. Point a browser at the hostname you picked and you should be greeted by the colorful login page.
-
-Doesn't work? Take a look at the [Troubleshooting]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/helm-rancher/troubleshooting/) Page
@@ -1,245 +0,0 @@
---
-title: Chart Options
-weight: 276
---
-
-### Common Options
-
-| Option | Default Value | Description |
-| --- | --- | --- |
-| `hostname` | " " | `string` - the Fully Qualified Domain Name for your Rancher Server |
-| `ingress.tls.source` | "rancher" | `string` - Where to get the cert for the ingress. - "rancher, letsEncrypt, secret" |
-| `letsEncrypt.email` | " " | `string` - Your email address |
-| `letsEncrypt.environment` | "production" | `string` - Valid options: "staging, production" |
-| `privateCA` | false | `bool` - Set to true if your cert is signed by a private CA |
-
-<br/>
-
-### Advanced Options
-
-| Option | Default Value | Description |
-| --- | --- | --- |
-| `additionalTrustedCAs` | false | `bool` - See [Additional Trusted CAs](#additional-trusted-cas) |
-| `addLocal` | "auto" | `string` - Have Rancher detect and import the "local" Rancher server cluster [Import "local Cluster](#import-local-cluster) |
-| `antiAffinity` | "preferred" | `string` - AntiAffinity rule for Rancher pods - "preferred, required" |
-| `auditLog.destination` | "sidecar" | `string` - Stream to sidecar container console or hostPath volume - "sidecar, hostPath" |
-| `auditLog.hostPath` | "/var/log/rancher/audit" | `string` - log file destination on host (only applies when `auditLog.destination` is set to `hostPath`) |
-| `auditLog.level` | 0 | `int` - set the [API Audit Log]({{<baseurl>}}/rancher/v2.x/en/installation/api-auditing) level. 0 is off. [0-3] |
-| `auditLog.maxAge` | 1 | `int` - maximum number of days to retain old audit log files (only applies when `auditLog.destination` is set to `hostPath`) |
-| `auditLog.maxBackups` | 1 | `int` - maximum number of audit log files to retain (only applies when `auditLog.destination` is set to `hostPath`) |
-| `auditLog.maxSize` | 100 | `int` - maximum size in megabytes of the audit log file before it gets rotated  (only applies when `auditLog.destination` is set to `hostPath`) |
-| `busyboxImage` | "busybox" | `string` - Image location for busybox image used to collect audit logs _Note: Available as of v2.2.0_ |
-| `debug` | false | `bool` - set debug flag on rancher server |
-| `extraEnv` | [] | `list` - set additional environment variables for Rancher _Note: Available as of v2.2.0_ |
-| `imagePullSecrets` | [] | `list` - list of names of Secret resource containing private registry credentials |
-| `ingress.extraAnnotations` | {} | `map` - additional annotations to customize the ingress |
-| `ingress.configurationSnippet` | "" | `string` - Add additional Nginx configuration. Can be used for proxy configuration. _Note: Available as of v2.0.15, v2.1.10 and v2.2.4_ |
-| `proxy` | "" | `string` -  HTTP[S] proxy server for Rancher |
-| `noProxy` | "127.0.0.0/8,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16" | `string` - comma separated list of hostnames or ip address not to use the proxy |
-| `resources` | {} | `map` - rancher pod resource requests & limits |
-| `rancherImage` | "rancher/rancher" | `string` - rancher image source |
-| `rancherImageTag` | same as chart version | `string` - rancher/rancher image tag |
-| `tls` | "ingress" | `string` - See [External TLS Termination](#external-tls-termination) for details. - "ingress, external" |
-| `systemDefaultRegistry` | "" | `string` - private registry to be used for all system Docker images, e.g., http://registry.example.com/ _Available as of v2.3.0_ |
-| `useBundledSystemChart` | `false` | `bool` - select to use the system-charts packaged with Rancher server. This option is used for air gapped installations. _Available as of v2.3.0_
-
-<br/>
-
-### API Audit Log
-
-Enabling the [API Audit Log]({{<baseurl>}}/rancher/v2.x/en/installation/api-auditing/).
-
-You can collect this log as you would any container log. Enable the [Logging service under Rancher Tools]({{<baseurl>}}/rancher/v2.x/en/cluster-admin/tools/logging/) for the `System` Project on the Rancher server cluster.
-
-```plain
--set auditLog.level=1
-```
-
-By default enabling Audit Logging will create a sidecar container in the Rancher pod. This container (`rancher-audit-log`) will stream the log to `stdout`.  You can collect this log as you would any container log. When using the sidecar as the audit log destination, the `hostPath`, `maxAge`, `maxBackups`, and `maxSize` options do not apply. It's advised to use your OS or Docker daemon's log rotation features to control disk space use. Enable the [Logging service under Rancher Tools]({{<baseurl>}}/rancher/v2.x/en/cluster-admin/tools/logging/) for the Rancher server cluster or System Project.
-
-Set the `auditLog.destination` to `hostPath` to forward logs to volume shared with the host system instead of streaming to a sidecar container. When setting the destination to `hostPath` you may want to adjust the other auditLog parameters for log rotation.
-
-### Setting Extra Environment Variables
-
-_Available as of v2.2.0_
-
-You can set extra environment variables for Rancher server using `extraEnv`. This list uses the same `name` and `value` keys as the container manifest definitions. Remember to quote the values.
-
-```plain
--set 'extraEnv[0].name=CATTLE_TLS_MIN_VERSION'
--set 'extraEnv[0].value=1.0'
-```
-
-### TLS settings
-
-_Available as of v2.2.0_
-
-To set a different TLS configuration, you can use the `CATTLE_TLS_MIN_VERSION` and `CATTLE_TLS_CIPHERS` environment variables. For example, to configure TLS 1.0 as minimum accepted TLS version:
-
-```plain
--set 'extraEnv[0].name=CATTLE_TLS_MIN_VERSION'
--set 'extraEnv[0].value=1.0'
-```
-
-See [TLS settings]({{<baseurl>}}/rancher/v2.x/en/admin-settings/tls-settings) for more information and options.
-
-### Import `local` Cluster
-
-By default Rancher server will detect and import the `local` cluster it's running on.  User with access to the `local` cluster will essentially have "root" access to all the clusters managed by Rancher server.
-
-If this is a concern in your environment you can set this option to "false" on your initial install.
-
-> Note: This option is only effective on the initial Rancher install. See [Issue 16522](https://github.com/rancher/rancher/issues/16522) for more information.
-
-```plain
--set addLocal="false"
-```
-
-### Customizing your Ingress
-
-To customize or use a different ingress with Rancher server you can set your own Ingress annotations.
-
-Example on setting a custom certificate issuer:
-
-```plain
--set ingress.extraAnnotations.'certmanager\.k8s\.io/cluster-issuer'=ca-key-pair
-```
-
-_Available as of v2.0.15, v2.1.10 and v2.2.4_
-
-Example on setting a static proxy header with `ingress.configurationSnippet`. This value is parsed like a template so variables can be used.
-
-```plain
--set ingress.configurationSnippet='more_set_input_headers X-Forwarded-Host {{ .Values.hostname }};'
-```
-
-### HTTP Proxy
-
-Rancher requires internet access for some functionality (helm charts). Use `proxy` to set your proxy server.
-
-Add your IP exceptions to the `noProxy` list. Make sure you add the Service cluster IP range (default: 10.43.0.1/16) and any worker cluster `controlplane` nodes. Rancher supports CIDR notation ranges in this list.
-
-```plain
--set proxy="http://<username>:<password>@<proxy_url>:<proxy_port>/"
--set noProxy="127.0.0.0/8\,10.0.0.0/8\,172.16.0.0/12\,192.168.0.0/16"
-```
-
-### Additional Trusted CAs
-
-If you have private registries, catalogs or a proxy that intercepts certificates, you may need to add additional trusted CAs to Rancher.
-
-```plain
--set additionalTrustedCAs=true
-```
-
-Once the Rancher deployment is created, copy your CA certs in pem format into a file named `ca-additional.pem` and use `kubectl` to create the `tls-ca-additional` secret in the `cattle-system` namespace.
-
-```plain
-kubectl -n cattle-system create secret generic tls-ca-additional --from-file=ca-additional.pem=./ca-additional.pem
-```
-
-### Private Registry and Air Gap Installs
-
-For details on installing Rancher with a private registry, see:
-
- [Air Gap: Docker Install]({{<baseurl>}}/rancher/v2.x/en/installation/air-gap-single-node/)
- [Air Gap: Kubernetes Install]({{<baseurl>}}/rancher/v2.x/en/installation/air-gap-high-availability/)
-
-
-### External TLS Termination
-
-We recommend configuring your load balancer as a Layer 4 balancer, forwarding plain 80/tcp and 443/tcp to the Rancher Management cluster nodes. The Ingress Controller on the cluster will redirect http traffic on port 80 to https on port 443.
-
-You may terminate the SSL/TLS on a L7 load balancer external to the Rancher cluster (ingress). Use the `--set tls=external` option and point your load balancer at port http 80 on all of the Rancher cluster nodes. This will expose the Rancher interface on http port 80. Be aware that clients that are allowed to connect directly to the Rancher cluster will not be encrypted. If you choose to do this we recommend that you restrict direct access at the network level to just your load balancer.
-
-> **Note:** If you are using a Private CA signed certificate, add `--set privateCA=true` and see [Adding TLS Secrets - Using a Private CA Signed Certificate]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/helm-rancher/tls-secrets/#using-a-private-ca-signed-certificate) to add the CA cert for Rancher.
-
-Your load balancer must support long lived websocket connections and will need to insert proxy headers so Rancher can route links correctly.
-
-#### Configuring Ingress for External TLS when Using NGINX v0.25
-
-In NGINX v0.25, the behavior of NGINX has [changed](https://github.com/kubernetes/ingress-nginx/blob/master/Changelog.md#0220) regarding forwarding headers and external TLS termination. Therefore, in the scenario that you are using external TLS termination configuration with NGINX v0.25, you must edit the `cluster.yml` to enable the `use-forwarded-headers` option for ingress:
-
-```yaml
-ingress:
-  provider: nginx
-  options:
-    use-forwarded-headers: "true"
-```
-
-#### Required Headers
-
-* `Host`
-* `X-Forwarded-Proto`
-* `X-Forwarded-Port`
-* `X-Forwarded-For`
-
-#### Recommended Timeouts
-
-* Read Timeout: `1800 seconds`
-* Write Timeout: `1800 seconds`
-* Connect Timeout: `30 seconds`
-
-#### Health Checks
-
-Rancher will respond `200` to health checks on the `/healthz` endpoint.
-
-
-#### Example NGINX config
-
-This NGINX configuration is tested on NGINX 1.14.
-
-  >**Note:** This NGINX configuration is only an example and may not suit your environment. For complete documentation, see [NGINX Load Balancing - HTTP Load Balancing](https://docs.nginx.com/nginx/admin-guide/load-balancer/http-load-balancer/).
-
-* Replace `IP_NODE1`, `IP_NODE2` and `IP_NODE3` with the IP addresses of the nodes in your cluster.
-* Replace both occurrences of `FQDN` to the DNS name for Rancher.
-* Replace `/certs/fullchain.pem` and `/certs/privkey.pem` to the location of the server certificate and the server certificate key respectively.
-
-```
-worker_processes 4;
-worker_rlimit_nofile 40000;
-
-events {
-    worker_connections 8192;
-}
-
-http {
-    upstream rancher {
-        server IP_NODE_1:80;
-        server IP_NODE_2:80;
-        server IP_NODE_3:80;
-    }
-
-    map $http_upgrade $connection_upgrade {
-        default Upgrade;
-        ''      close;
-    }
-
-    server {
-        listen 443 ssl http2;
-        server_name FQDN;
-        ssl_certificate /certs/fullchain.pem;
-        ssl_certificate_key /certs/privkey.pem;
-
-        location / {
-            proxy_set_header Host $host;
-            proxy_set_header X-Forwarded-Proto $scheme;
-            proxy_set_header X-Forwarded-Port $server_port;
-            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
-            proxy_pass http://rancher;
-            proxy_http_version 1.1;
-            proxy_set_header Upgrade $http_upgrade;
-            proxy_set_header Connection $connection_upgrade;
-            # This allows the ability for the execute shell window to remain open for up to 15 minutes. Without this parameter, the default is 1 minute and will automatically close.
-            proxy_read_timeout 900s;
-            proxy_buffering off;
-        }
-    }
-
-    server {
-        listen 80;
-        server_name FQDN;
-        return 301 https://$server_name$request_uri;
-    }
-}
-```
@@ -1,33 +0,0 @@
---
-title: Adding Kubernetes TLS Secrets
-description: Read about how to populate the Kubernetes TLS secret for a Rancher installation  
-weight: 276
---
-
-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. 
-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.
-
-```
-kubectl -n cattle-system create secret tls tls-rancher-ingress \
-  --cert=tls.crt \
-  --key=tls.key
-```
-
-> **Note:** If you want to replace the certificate, you can delete the `tls-rancher-ingress` secret using `kubectl -n cattle-system delete secret tls-rancher-ingress` and add a new one using the command shown above. If you are using a private CA signed certificate, replacing the certificate is only possible if the new certificate is signed by the same CA as the certificate currently in use.
-
-### Using a Private CA Signed Certificate
-
-If you are using a private CA, Rancher requires a copy of the CA certificate which is used by the Rancher Agent to validate the connection to the server.
-
-Copy the CA certificate into a file named `cacerts.pem` and use `kubectl` to create the `tls-ca` secret in the `cattle-system` namespace.
-
-```
-kubectl -n cattle-system create secret generic tls-ca \
-  --from-file=cacerts.pem=./cacerts.pem
-```
@@ -1,133 +0,0 @@
---
-title: Troubleshooting
-weight: 276
---
-
-### Where is everything
-
-Most of the troubleshooting will be done on objects in these 3 namespaces.
-
-* `cattle-system` - `rancher` deployment and pods.
-* `ingress-nginx` - Ingress controller pods and services.
-* `kube-system` - `tiller` and `cert-manager` pods.
-
-### "default backend - 404"
-
-A number of things can cause the ingress-controller not to forward traffic to your rancher instance. Most of the time its due to a bad ssl configuration.
-
-Things to check
-
-* [Is Rancher Running](#is-rancher-running)
-* [Cert CN is "Kubernetes Ingress Controller Fake Certificate"](#cert-cn-is-kubernetes-ingress-controller-fake-certificate)
-
-### Is Rancher Running
-
-Use `kubectl` to check the `cattle-system` system namespace and see if the Rancher pods are in a Running state.
-
-```
-kubectl -n cattle-system get pods
-
-NAME                           READY     STATUS    RESTARTS   AGE
-pod/rancher-784d94f59b-vgqzh   1/1       Running   0          10m
-```
-
-If the state is not `Running`, run a `describe` on the pod and check the Events.
-
-```
-kubectl -n cattle-system describe pod
-
-...
-Events:
-  Type     Reason                 Age   From                Message
-  ----     ------                 ----  ----                -------
-  Normal   Scheduled              11m   default-scheduler   Successfully assigned rancher-784d94f59b-vgqzh to localhost
-  Normal   SuccessfulMountVolume  11m   kubelet, localhost  MountVolume.SetUp succeeded for volume "rancher-token-dj4mt"
-  Normal   Pulling                11m   kubelet, localhost  pulling image "rancher/rancher:v2.0.4"
-  Normal   Pulled                 11m   kubelet, localhost  Successfully pulled image "rancher/rancher:v2.0.4"
-  Normal   Created                11m   kubelet, localhost  Created container
-  Normal   Started                11m   kubelet, localhost  Started container
-```
-
-### Checking the rancher logs
-
-Use `kubectl` to list the pods.
-
-```
-kubectl -n cattle-system get pods
-
-NAME                           READY     STATUS    RESTARTS   AGE
-pod/rancher-784d94f59b-vgqzh   1/1       Running   0          10m
-```
-
-Use `kubectl` and the pod name to list the logs from the pod.
-
-```
-kubectl -n cattle-system logs -f rancher-784d94f59b-vgqzh
-```
-
-### Cert CN is "Kubernetes Ingress Controller Fake Certificate"
-
-Use your browser to check the certificate details. If it says the Common Name is "Kubernetes Ingress Controller Fake Certificate", something may have gone wrong with reading or issuing your SSL cert.
-
-> **Note:** if you are using LetsEncrypt to issue certs it can sometimes take a few minuets to issue the cert.
-
-#### cert-manager issued certs (Rancher Generated or LetsEncrypt)
-
-`cert-manager` has 3 parts.
-
-* `cert-manager` pod in the `kube-system` namespace.
-* `Issuer` object in the `cattle-system` namespace.
-* `Certificate` object in the `cattle-system` namespace.
-
-Work backwards and do a `kubectl describe` on each object and check the events. You can track down what might be missing.
-
-For example there is a problem with the Issuer:
-
-```
-kubectl -n cattle-system describe certificate
-...
-Events:
-  Type     Reason          Age                 From          Message
-  ----     ------          ----                ----          -------
-  Warning  IssuerNotReady  18s (x23 over 19m)  cert-manager  Issuer rancher not ready
-```
-
-```
-kubectl -n cattle-system describe issuer
-...
-Events:
-  Type     Reason         Age                 From          Message
-  ----     ------         ----                ----          -------
-  Warning  ErrInitIssuer  19m (x12 over 19m)  cert-manager  Error initializing issuer: secret "tls-rancher" not found
-  Warning  ErrGetKeyPair  9m (x16 over 19m)   cert-manager  Error getting keypair for CA issuer: secret "tls-rancher" not found
-```
-
-#### Bring Your Own SSL Certs
-
-Your certs get applied directly to the Ingress object in the `cattle-system` namespace.
-
-Check the status of the Ingress object and see if its ready.
-
-```
-kubectl -n cattle-system describe ingress
-```
-
-If its ready and the SSL is still not working you may have a malformed cert or secret.
-
-Check the nginx-ingress-controller logs. Because the nginx-ingress-controller has multiple containers in its pod you will need to specify the name of the container.
-
-```
-kubectl -n ingress-nginx logs -f nginx-ingress-controller-rfjrq nginx-ingress-controller
-...
-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
-```
-
-### no matches for kind "Issuer"
-
-The [SSL configuration]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/helm-rancher/#choose-your-ssl-configuration) option you have chosen requires [cert-manager]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/helm-rancher/#optional-install-cert-manager) to be installed before installing Rancher or else the following error is shown:
-
-```
-Error: validation failed: unable to recognize "": no matches for kind "Issuer" in version "certmanager.k8s.io/v1alpha1"
-```
-
-Install [cert-manager]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/helm-rancher/#optional-install-cert-manager) and try installing Rancher again.
@@ -1,132 +0,0 @@
---
-title: "2. Install Kubernetes with RKE"
-weight: 190
---
-
-Use RKE to install Kubernetes with a high availability etcd configuration.
-
->**Note:** For systems without direct internet access see [Air Gap: Kubernetes install]({{<baseurl>}}/rancher/v2.x/en/installation/air-gap-high-availability/) for install details.
-
-### Create the `rancher-cluster.yml` File
-
-Using the sample below create the `rancher-cluster.yml` file. Replace the IP Addresses in the `nodes` list with the IP address or DNS names of the 3 nodes you created.
-
-> **Note:**  If your node has public and internal addresses, it is recommended to set the `internal_address:` so Kubernetes will use it for intra-cluster communication.  Some services like AWS EC2 require setting the `internal_address:` if you want to use self-referencing security groups or firewalls.
-
-
-```yaml
-nodes:
-  - address: 165.227.114.63
-    internal_address: 172.16.22.12
-    user: ubuntu
-    role: [controlplane,worker,etcd]
-  - address: 165.227.116.167
-    internal_address: 172.16.32.37
-    user: ubuntu
-    role: [controlplane,worker,etcd]
-  - address: 165.227.127.226
-    internal_address: 172.16.42.73
-    user: ubuntu
-    role: [controlplane,worker,etcd]
-
-services:
-  etcd:
-    snapshot: true
-    creation: 6h
-    retention: 24h
-```
-
-#### Common RKE Nodes Options
-
-| Option | Required | Description |
-| --- | --- | --- |
-| `address` | yes | The public DNS or IP address |
-| `user` | yes | A user that can run docker commands |
-| `role` | yes | List of Kubernetes roles assigned to the node |
-| `internal_address` | no | The private DNS or IP address for internal cluster traffic |
-| `ssh_key_path` | no | Path to SSH private key used to authenticate to the node (defaults to `~/.ssh/id_rsa`) |
-
-#### Advanced Configurations
-
-RKE has many configuration options for customizing the install to suit your specific environment.
-
-Please see the [RKE Documentation]({{<baseurl>}}/rke/latest/en/config-options/) for the full list of options and capabilities.
-
-For tuning your etcd cluster for larger Rancher installations see the [etcd settings guide]({{<baseurl>}}/rancher/v2.x/en/installation/options/etcd/).
-
-### Run RKE
-
-```
-rke up --config ./rancher-cluster.yml
-```
-
-When finished, it should end with the line: `Finished building Kubernetes cluster successfully`.
-
-### Testing Your Cluster
-
-RKE should have created a file `kube_config_rancher-cluster.yml`. This file has the credentials for `kubectl` and `helm`.
-
-> **Note:** If you have used a different file name from `rancher-cluster.yml`, then the kube config file will be named `kube_config_<FILE_NAME>.yml`.
-
-You can copy this file to `$HOME/.kube/config` or if you are working with multiple Kubernetes clusters, set the `KUBECONFIG` environmental variable to the path of `kube_config_rancher-cluster.yml`.
-
-```
-export KUBECONFIG=$(pwd)/kube_config_rancher-cluster.yml
-```
-
-Test your connectivity with `kubectl` and see if all your nodes are in `Ready` state.
-
-```
-kubectl get nodes
-
-NAME                          STATUS    ROLES                      AGE       VERSION
-165.227.114.63                Ready     controlplane,etcd,worker   11m       v1.13.5
-165.227.116.167               Ready     controlplane,etcd,worker   11m       v1.13.5
-165.227.127.226               Ready     controlplane,etcd,worker   11m       v1.13.5
-```
-
-### Check the Health of Your Cluster Pods
-
-Check that all the required pods and containers are healthy are ready to continue.
-
-* Pods are in `Running` or `Completed` state.
-* `READY` column shows all the containers are running (i.e. `3/3`) for pods with `STATUS` `Running`
-* Pods with `STATUS` `Completed` are run-once Jobs. For these pods `READY` should be `0/1`.
-
-```
-kubectl get pods --all-namespaces
-
-NAMESPACE       NAME                                      READY     STATUS      RESTARTS   AGE
-ingress-nginx   nginx-ingress-controller-tnsn4            1/1       Running     0          30s
-ingress-nginx   nginx-ingress-controller-tw2ht            1/1       Running     0          30s
-ingress-nginx   nginx-ingress-controller-v874b            1/1       Running     0          30s
-kube-system     canal-jp4hz                               3/3       Running     0          30s
-kube-system     canal-z2hg8                               3/3       Running     0          30s
-kube-system     canal-z6kpw                               3/3       Running     0          30s
-kube-system     kube-dns-7588d5b5f5-sf4vh                 3/3       Running     0          30s
-kube-system     kube-dns-autoscaler-5db9bbb766-jz2k6      1/1       Running     0          30s
-kube-system     metrics-server-97bc649d5-4rl2q            1/1       Running     0          30s
-kube-system     rke-ingress-controller-deploy-job-bhzgm   0/1       Completed   0          30s
-kube-system     rke-kubedns-addon-deploy-job-gl7t4        0/1       Completed   0          30s
-kube-system     rke-metrics-addon-deploy-job-7ljkc        0/1       Completed   0          30s
-kube-system     rke-network-plugin-deploy-job-6pbgj       0/1       Completed   0          30s
-```
-
-### Save Your Files
-
-> **Important**
-> The files mentioned below are needed to maintain, troubleshoot and upgrade your cluster.
-
-Save a copy of the following files in a secure location:
-
- `rancher-cluster.yml`: The RKE cluster configuration file.
- `kube_config_rancher-cluster.yml`: The [Kubeconfig file]({{<baseurl>}}/rke/latest/en/kubeconfig/) for the cluster, this file contains credentials for full access to the cluster.
- `rancher-cluster.rkestate`: The [Kubernetes Cluster State file]({{<baseurl>}}/rke/latest/en/installation/#kubernetes-cluster-state), this file contains credentials for full access to the cluster.<br/><br/>_The Kubernetes Cluster State file is only created when using RKE v0.2.0 or higher._
-
-> **Note:** The "rancher-cluster" parts of the two latter file names are dependent on how you name the RKE cluster configuration file.
-
-### Issues or errors?
-
-See the [Troubleshooting]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/kubernetes-rke/troubleshooting/) page.
-
-### [Next: Initialize Helm (Install tiller)]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/helm-init/)
@@ -1,52 +0,0 @@
---
-title: Troubleshooting
-weight: 276
---
-
-### canal Pods show READY 2/3
-
-The most common cause of this issue is port 8472/UDP is not open between the nodes. Check your local firewall, network routing or security groups.
-
-Once the network issue is resolved, the `canal` pods should timeout and restart to establish their connections.
-
-### nginx-ingress-controller Pods show RESTARTS
-
-The most common cause of this issue is the `canal` pods have failed to establish the overlay network. See [canal Pods show READY `2/3`](#canal-pods-show-ready-2-3) for troubleshooting.
-
-### Failed to set up SSH tunneling for host [xxx.xxx.xxx.xxx]: Can't retrieve Docker Info
-
-#### Failed to dial to /var/run/docker.sock: ssh: rejected: administratively prohibited (open failed)
-
-* User specified to connect with does not have permission to access the Docker socket. This can be checked by logging into the host and running the command `docker ps`:
-
-```
-$ ssh user@server
-user@server$ docker ps
-CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS                    NAMES
-```
-
-See [Manage Docker as a non-root user](https://docs.docker.com/install/linux/linux-postinstall/#manage-docker-as-a-non-root-user) how to set this up properly.
-
-* When using RedHat/CentOS as operating system, you cannot use the user `root` to connect to the nodes because of [Bugzilla #1527565](https://bugzilla.redhat.com/show_bug.cgi?id=1527565). You will need to add a separate user and configure it to access the Docker socket. See [Manage Docker as a non-root user](https://docs.docker.com/install/linux/linux-postinstall/#manage-docker-as-a-non-root-user) how to set this up properly.
-
-* SSH server version is not version 6.7 or higher. This is needed for socket forwarding to work, which is used to connect to the Docker socket over SSH. This can be checked using `sshd -V` on the host you are connecting to, or using netcat:
-```
-$ 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
-
-* The key file specified as `ssh_key_path` cannot be accessed. Make sure that you specified the private key file (not the public key, `.pub`), and that the user that is running the `rke` command can access the private key file.
-
-#### 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
-
-* The key file specified as `ssh_key_path` is not correct for accessing the node. Double-check if you specified the correct `ssh_key_path` for the node and if you specified the correct user to connect with.
-
-#### Failed to dial ssh using address [xxx.xxx.xxx.xxx:xx]: Error configuring SSH: ssh: cannot decode encrypted private keys
-
-* If you want to use encrypted private keys, you should use `ssh-agent` to load your keys with your passphrase. If the `SSH_AUTH_SOCK` environment variable is found in the environment where the `rke` command is run, it will be used automatically to connect to the node.
-
-#### Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
-
-* The node is not reachable on the configured `address` and `port`.
@@ -1,16 +0,0 @@
---
-title: RKE Add-On Install
-weight: 276
---
-
-> #### **Important: RKE add-on install is only supported up to Rancher v2.0.8**
->
->Please use the Rancher helm chart to install Rancher on a Kubernetes cluster. For details, see the [Kubernetes Install - Installation Outline]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/#installation-outline).
->
->If you are currently using the RKE add-on install method, see [Migrating from a Kubernetes Install with an RKE Add-on]({{<baseurl>}}/rancher/v2.x/en/upgrades/upgrades/migrating-from-rke-add-on/) for details on how to move to using the helm chart.
-
-
-* [Kubernetes installation with External Load Balancer (TCP/Layer 4)]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/rke-add-on/layer-4-lb)
-* [Kubernetes installation with External Load Balancer (HTTPS/Layer 7)]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/rke-add-on/layer-7-lb)
-* [HTTP Proxy Configuration for a Kubernetes installation]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/rke-add-on/proxy/)
-* [Troubleshooting RKE Add-on Installs]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/rke-add-on/troubleshooting/)
@@ -1,55 +0,0 @@
---
-title: Enable API Auditing
-weight: 300
-aliases:
-  - /rke/latest/en/config-options/add-ons/api-auditing/
---
-
->**Important: RKE add-on install is only supported up to Rancher v2.0.8**
->
->Please use the Rancher Helm chart to install Rancher on a Kubernetes cluster. For details, see the [Kubernetes Install - Installation Outline]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/#installation-outline).
->
->If you are currently using the RKE add-on install method, see [Migrating from a Kubernetes Install with an RKE Add-on]({{<baseurl>}}/rancher/v2.x/en/upgrades/upgrades/migrating-from-rke-add-on/) for details on how to move to using the helm chart.
-
-If you're using RKE to install Rancher, you can use directives to enable API Auditing for your Rancher install. You can know what happened, when it happened, who initiated it, and what cluster it affected. API auditing records all requests and responses to and from the Rancher API, which includes use of the Rancher UI and any other use of the Rancher API through programmatic use.
-
-## In-line Arguments
-
-Enable API Auditing using RKE by adding arguments to your Rancher container.
-
-To enable API auditing:
-
- Add API Auditing arguments (`args`) to your Rancher container.
- Declare a `mountPath` in the `volumeMounts` directive of the container.
- Declare a `path` in the `volumes` directive.
-
-For more information about each argument, its syntax, and how to view API Audit logs, see [Rancher v2.0 Documentation: API Auditing]({{<baseurl>}}/rancher/v2.x/en/installation/api-auditing).
-
-```yaml
-...
-containers:
-        - image: rancher/rancher:latest
-          imagePullPolicy: Always
-          name: cattle-server
-          args: ["--audit-log-path", "/var/log/auditlog/rancher-api-audit.log", "--audit-log-maxbackup", "5", "--audit-log-maxsize", "50", "--audit-level", "2"]
-          ports:
-          - containerPort: 80
-            protocol: TCP
-          - containerPort: 443
-            protocol: TCP
-          volumeMounts:
-          - mountPath: /etc/rancher/ssl
-            name: cattle-keys-volume
-            readOnly: true
-          - mountPath: /var/log/auditlog
-            name: audit-log-dir
-        volumes:
-        - name: cattle-keys-volume
-          secret:
-            defaultMode: 420
-            secretName: cattle-keys-server
-        - name: audit-log-dir
-          hostPath:
-            path: /var/log/rancher/auditlog
-            type: Directory
-```
@@ -1,400 +0,0 @@
---
-title: Kubernetes Install with External Load Balancer (TCP/Layer 4)
-weight: 275
---
-
-> #### **Important: RKE add-on install is only supported up to Rancher v2.0.8**
->
->Please use the Rancher helm chart to install Rancher on a Kubernetes cluster. For details, see the [Kubernetes Install - Installation Outline]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/#installation-outline).
->
->If you are currently using the RKE add-on install method, see [Migrating from a High-availability Kubernetes install with an RKE add-on]({{<baseurl>}}/rancher/v2.x/en/upgrades/upgrades/migrating-from-rke-add-on/) for details on how to move to using the Helm chart.
-
-This procedure walks you through setting up a 3-node cluster using the Rancher Kubernetes Engine (RKE). The cluster's sole purpose is running pods for Rancher. The setup is based on:
-
- Layer 4 load balancer (TCP)
- [NGINX ingress controller with SSL termination (HTTPS)](https://kubernetes.github.io/ingress-nginx/)
-
-In a Kubernetes setup that uses a layer 4 load balancer, the load balancer accepts Rancher client connections over the TCP/UDP protocols (i.e., the transport level). The load balancer then forwards these connections to individual cluster nodes without reading the request itself. Because the load balancer cannot read the packets it's forwarding, the routing decisions it can make are limited.
-
-<sup>Kubernetes Rancher install with layer 4 load balancer, depicting SSL termination at ingress controllers</sup>
-![High-availability Kubernetes installation of Rancher]({{<baseurl>}}/img/rancher/ha/rancher2ha.svg)
-
-## Installation Outline
-
-Installation of Rancher in a high-availability configuration involves multiple procedures. Review this outline to learn about each procedure you need to complete.
-
-<!-- TOC -->
-
- [1. Provision Linux Hosts](#1-provision-linux-hosts)
- [2. Configure Load Balancer](#2-configure-load-balancer)
- [3. Configure DNS](#3-configure-dns)
- [4. Install RKE](#4-install-rke)
- [5. Download RKE Config File Template](#5-download-rke-config-file-template)
- [6. Configure Nodes](#6-configure-nodes)
- [7. Configure Certificates](#7-configure-certificates)
- [8. Configure FQDN](#8-configure-fqdn)
- [9. Configure Rancher version](#9-configure-rancher-version)
- [10. Back Up Your RKE Config File](#10-back-up-your-rke-config-file)
- [11. Run RKE](#11-run-rke)
- [12. Back Up Auto-Generated Config File](#12-back-up-auto-generated-config-file)
-
-<!-- /TOC -->
-
-<br/>
-
-## 1. Provision Linux Hosts
-
-Provision three Linux hosts according to our [Requirements]({{<baseurl>}}/rancher/v2.x/en/installation/requirements).
-
-## 2. Configure Load Balancer
-
-We will be using NGINX as our Layer 4 Load Balancer (TCP). NGINX will forward all connections to one of your Rancher nodes. If you want to use Amazon NLB, you can skip this step and use [Amazon NLB configuration]({{<baseurl>}}/rancher/v2.x/en/installation/k8s-install-server-install/nlb/)
-
->**Note:**
-> In this configuration, the load balancer is positioned in front of your Linux hosts. The load balancer can be any host that you have available that's capable of running NGINX.
->
->One caveat: do not use one of your Rancher nodes as the load balancer.
-
-### A. Install NGINX
-
-Start by installing NGINX on your load balancer host. NGINX has packages available for all known operating systems. For help installing NGINX, refer to their [install documentation](https://www.nginx.com/resources/wiki/start/topics/tutorials/install/).
-
-The `stream` module is required, which is present when using the official NGINX packages. Please refer to your OS documentation how to install and enable the NGINX `stream` module on your operating system.
-
-### B. Create NGINX Configuration
-
-After installing NGINX, you need to update the NGINX config file, `nginx.conf`, with the IP addresses for your nodes.
-
-1. Copy and paste the code sample below into your favorite text editor. Save it as `nginx.conf`.
-
-2. From `nginx.conf`, replace `IP_NODE_1`, `IP_NODE_2`, and `IP_NODE_3` with the IPs of your [Linux hosts](#1-provision-linux-hosts).
-
-    >**Note:** This Nginx configuration is only an example and may not suit your environment. For complete documentation, see [NGINX Load Balancing - TCP and UDP Load Balancer](https://docs.nginx.com/nginx/admin-guide/load-balancer/tcp-udp-load-balancer/).
-
-    **Example NGINX config:**
-    ```
-    worker_processes 4;
-    worker_rlimit_nofile 40000;
-
-    events {
-        worker_connections 8192;
-    }
-
-    http {
-        server {
-            listen         80;
-            return 301 https://$host$request_uri;
-        }
-    }
-
-    stream {
-        upstream rancher_servers {
-            least_conn;
-            server IP_NODE_1:443 max_fails=3 fail_timeout=5s;
-            server IP_NODE_2:443 max_fails=3 fail_timeout=5s;
-            server IP_NODE_3:443 max_fails=3 fail_timeout=5s;
-        }
-        server {
-            listen     443;
-            proxy_pass rancher_servers;
-        }
-    }
-    ```
-
-3. Save `nginx.conf` to your load balancer at the following path: `/etc/nginx/nginx.conf`.
-
-4. Load the updates to your NGINX configuration by running the following command:
-
-    ```
-    # nginx -s reload
-    ```
-
-### Option - Run NGINX as Docker container
-
-Instead of installing NGINX as a package on the operating system, you can rather run it as a Docker container. Save the edited **Example NGINX config** as `/etc/nginx.conf` and run the following command to launch the NGINX container:
-
-```
-docker run -d --restart=unless-stopped \
-  -p 80:80 -p 443:443 \
-  -v /etc/nginx.conf:/etc/nginx/nginx.conf \
-  nginx:1.14
-```
-
-## 3. Configure DNS
-
-Choose a fully qualified domain name (FQDN) that you want to use to access Rancher (e.g., `rancher.yourdomain.com`).<br/><br/>
-
-1. Log into your DNS server a create a `DNS A` record that points to the IP address of your [load balancer](#2-configure-load-balancer).
-
-2. Validate that the `DNS A` is working correctly. Run the following command from any terminal, replacing `HOSTNAME.DOMAIN.COM` with your chosen FQDN:
-
-    `nslookup HOSTNAME.DOMAIN.COM`
-
-    **Step Result:** Terminal displays output similar to the following:
-
-    ```
-    $ nslookup rancher.yourdomain.com
-    Server:         YOUR_HOSTNAME_IP_ADDRESS
-    Address:        YOUR_HOSTNAME_IP_ADDRESS#53
-
-    Non-authoritative answer:
-    Name:   rancher.yourdomain.com
-    Address: HOSTNAME.DOMAIN.COM
-    ```
-
-<br/>
-
-## 4. Install RKE
-
-RKE (Rancher Kubernetes Engine) is a fast, versatile Kubernetes installer that you can use to install Kubernetes on your Linux hosts. We will use RKE to setup our cluster and run Rancher.
-
-1. Follow the [RKE Install]({{<baseurl>}}/rke/latest/en/installation) instructions.
-
-2. Confirm that RKE is now executable by running the following command:
-
-    ```
-    rke --version
-    ```
-
-## 5. Download RKE Config File Template
-
-RKE uses a `.yml` config file to install and configure your Kubernetes cluster. There are 2 templates to choose from, depending on the SSL certificate you want to use.
-
-1. Download one of following templates, depending on the SSL certificate you're using.
-
-	- [Template for self-signed certificate<br/> `3-node-certificate.yml`]({{<baseurl>}}/rancher/v2.x/en/installation/options/cluster-yml-templates/3-node-certificate)
-	- [Template for certificate signed by recognized CA<br/> `3-node-certificate-recognizedca.yml`]({{<baseurl>}}/rancher/v2.x/en/installation/options/cluster-yml-templates/3-node-certificate-recognizedca)
-
-    >**Advanced Config Options:**
-    >
-    >- Want records of all transactions with the Rancher API? Enable the [API Auditing]({{<baseurl>}}/rancher/v2.x/en/installation/api-auditing) feature by editing your RKE config file. For more information, see how to enable it in [your RKE config file]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/rke-add-on/api-auditing/).
-    >- Want to know the other config options available for your RKE template? See the [RKE Documentation: Config Options]({{<baseurl>}}/rke/latest/en/config-options/).
-
-
-2. Rename the file to `rancher-cluster.yml`.
-
-## 6. Configure Nodes
-
-Once you have the `rancher-cluster.yml` config file template, edit the nodes section to point toward your Linux hosts.
-
-1. Open `rancher-cluster.yml` in your favorite text editor.
-
-1. Update the `nodes` section with the information of your [Linux hosts](#1-provision-linux-hosts).
-
-    For each node in your cluster, update the following placeholders: `IP_ADDRESS_X` and `USER`. The specified user should be able to access the Docket socket, you can test this by logging in with the specified user and run `docker ps`.
-
-    >**Note:**
-    > When using RHEL/CentOS, the SSH user can't be root due to https://bugzilla.redhat.com/show_bug.cgi?id=1527565. See [Operating System Requirements]({{<baseurl>}}/rke/latest/en/installation/os#redhat-enterprise-linux-rhel-centos) >for RHEL/CentOS specific requirements.
-
-        nodes:
-            # The IP address or hostname of the node
-        - address: IP_ADDRESS_1
-            # User that can login to the node and has access to the Docker socket (i.e. can execute `docker ps` on the node)
-            # When using RHEL/CentOS, this can't be root due to https://bugzilla.redhat.com/show_bug.cgi?id=1527565
-            user: USER
-            role: [controlplane,etcd,worker]
-            # Path the SSH key that can be used to access to node with the specified user
-            ssh_key_path: ~/.ssh/id_rsa
-        - address: IP_ADDRESS_2
-            user: USER
-            role: [controlplane,etcd,worker]
-            ssh_key_path: ~/.ssh/id_rsa
-        - address: IP_ADDRESS_3
-            user: USER
-            role: [controlplane,etcd,worker]
-            ssh_key_path: ~/.ssh/id_rsa
-
-1. **Optional:** By default, `rancher-cluster.yml` is configured to take backup snapshots of your data. To disable these snapshots, change the `backup` directive setting to `false`, as depicted below.
-
-        services:
-          etcd:
-            backup: false
-
-
-## 7. Configure Certificates
-
-For security purposes, SSL (Secure Sockets Layer) is required when using Rancher. SSL secures all Rancher network communication, like when you login or interact with a cluster.
-
-Choose from the following options:
-
-{{% accordion id="option-a" label="Option A—Bring Your Own Certificate: Self-Signed" %}}
-
->**Prerequisites:**
->Create a self-signed certificate.
->
->- The certificate files must be in [PEM format](#pem).
->- The certificate files must be encoded in [base64](#base64).
->- In your certificate file, include all intermediate certificates in the chain. Order your certificates with your certificate first, followed by the intermediates. For an example, see [Intermediate Certificates](#cert-order).
-
-1. In `kind: Secret` with `name: cattle-keys-ingress`:
-
-    * Replace `<BASE64_CRT>` with the base64 encoded string of the Certificate file (usually called `cert.pem` or `domain.crt`)
-    * Replace `<BASE64_KEY>` with the base64 encoded string of the Certificate Key file (usually called `key.pem` or `domain.key`)
-
-    >**Note:**
-    > The base64 encoded string should be on the same line as `tls.crt` or `tls.key`, without any newline at the beginning, in between or at the end.
-
-    **Step Result:** After replacing the values, the file should look like the example below (the base64 encoded strings should be different):
-
-    ```yaml
-    ---
-    apiVersion: v1
-    kind: Secret
-    metadata:
-        name: cattle-keys-ingress
-        namespace: cattle-system
-    type: Opaque
-    data:
-        tls.crt: LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUM1RENDQWN5Z0F3SUJBZ0lKQUlHc25NeG1LeGxLTUEwR0NTcUdTSWIzRFFFQkN3VUFNQkl4RURBT0JnTlYKQkFNTUIzUmxjM1F0WTJFd0hoY05NVGd3TlRBMk1qRXdOREE1V2hjTk1UZ3dOekExTWpFd05EQTVXakFXTVJRdwpFZ1lEVlFRRERBdG9ZUzV5Ym1Ob2NpNXViRENDQVNJd0RRWUpLb1pJaHZjTkFRRUJCUUFEZ2dFUEFEQ0NBUW9DCmdnRUJBTFJlMXdzekZSb2Rib2pZV05DSHA3UkdJaUVIMENDZ1F2MmdMRXNkUUNKZlcrUFEvVjM0NnQ3bSs3TFEKZXJaV3ZZMWpuY2VuWU5JSGRBU0VnU0ducWExYnhUSU9FaE0zQXpib3B0WDhjSW1OSGZoQlZETGdiTEYzUk0xaQpPM1JLTGdIS2tYSTMxZndjbU9zWGUwaElYQnpUbmxnM20vUzlXL3NTc0l1dDVwNENDUWV3TWlpWFhuUElKb21lCmpkS3VjSHFnMTlzd0YvcGVUalZrcVpuMkJHazZRaWFpMU41bldRV0pjcThTenZxTTViZElDaWlwYU9hWWQ3RFEKYWRTejV5dlF0YkxQNW4wTXpnOU43S3pGcEpvUys5QWdkWDI5cmZqV2JSekp3RzM5R3dRemN6VWtLcnZEb05JaQo0UFJHc01yclFNVXFSYjRSajNQOEJodEMxWXNDQXdFQUFhTTVNRGN3Q1FZRFZSMFRCQUl3QURBTEJnTlZIUThFCkJBTUNCZUF3SFFZRFZSMGxCQll3RkFZSUt3WUJCUVVIQXdJR0NDc0dBUVVGQndNQk1BMEdDU3FHU0liM0RRRUIKQ3dVQUE0SUJBUUNKZm5PWlFLWkowTFliOGNWUW5Vdi9NZkRZVEJIQ0pZcGM4MmgzUGlXWElMQk1jWDhQRC93MgpoOUExNkE4NGNxODJuQXEvaFZYYy9JNG9yaFY5WW9jSEg5UlcvbGthTUQ2VEJVR0Q1U1k4S292MHpHQ1ROaDZ6Ci9wZTNqTC9uU0pYSjRtQm51czJheHFtWnIvM3hhaWpYZG9kMmd3eGVhTklvRjNLbHB2aGU3ZjRBNmpsQTM0MmkKVVlCZ09iN1F5KytRZWd4U1diSmdoSzg1MmUvUUhnU2FVSkN6NW1sNGc1WndnNnBTUXhySUhCNkcvREc4dElSYwprZDMxSk1qY25Fb1Rhc1Jyc1NwVmNGdXZyQXlXN2liakZyYzhienBNcE1obDVwYUZRcEZzMnIwaXpZekhwakFsCk5ZR2I2OHJHcjBwQkp3YU5DS2ErbCtLRTk4M3A3NDYwCi0tLS0tRU5EIENFUlRJRklDQVRFLS0tLS0K
-        tls.key: LS0tLS1CRUdJTiBSU0EgUFJJVkFURSBLRVktLS0tLQpNSUlFb3dJQkFBS0NBUUVBdEY3WEN6TVZHaDF1aU5oWTBJZW50RVlpSVFmUUlLQkMvYUFzU3gxQUlsOWI0OUQ5ClhmanEzdWI3c3RCNnRsYTlqV09keDZkZzBnZDBCSVNCSWFlcHJWdkZNZzRTRXpjRE51aW0xZnh3aVkwZCtFRlUKTXVCc3NYZEV6V0k3ZEVvdUFjcVJjamZWL0J5WTZ4ZDdTRWhjSE5PZVdEZWI5TDFiK3hLd2k2M21uZ0lKQjdBeQpLSmRlYzhnbWlaNk4wcTV3ZXFEWDJ6QVgrbDVPTldTcG1mWUVhVHBDSnFMVTNtZFpCWWx5cnhMTytvemx0MGdLCktLbG81cGgzc05CcDFMUG5LOUMxc3MvbWZRek9EMDNzck1Xa21oTDcwQ0IxZmIydCtOWnRITW5BYmYwYkJETnoKTlNRcXU4T2cwaUxnOUVhd3l1dEF4U3BGdmhHUGMvd0dHMExWaXdJREFRQUJBb0lCQUJKYUErOHp4MVhjNEw0egpwUFd5bDdHVDRTMFRLbTNuWUdtRnZudjJBZXg5WDFBU2wzVFVPckZyTnZpK2xYMnYzYUZoSFZDUEN4N1RlMDVxClhPa2JzZnZkZG5iZFQ2RjgyMnJleVByRXNINk9TUnBWSzBmeDVaMDQwVnRFUDJCWm04eTYyNG1QZk1vbDdya2MKcm9Kd09rOEVpUHZZekpsZUd0bTAwUm1sRysyL2c0aWJsOTVmQXpyc1MvcGUyS3ZoN2NBVEtIcVh6MjlpUmZpbApiTGhBamQwcEVSMjNYU0hHR1ZqRmF3amNJK1c2L2RtbDZURDhrSzFGaUtldmJKTlREeVNXQnpPbXRTYUp1K01JCm9iUnVWWG4yZVNoamVGM1BYcHZRMWRhNXdBa0dJQWxOWjRHTG5QU2ZwVmJyU0plU3RrTGNzdEJheVlJS3BWZVgKSVVTTHM0RUNnWUVBMmNnZUE2WHh0TXdFNU5QWlNWdGhzbXRiYi9YYmtsSTdrWHlsdk5zZjFPdXRYVzkybVJneQpHcEhUQ0VubDB0Z1p3T081T1FLNjdFT3JUdDBRWStxMDJzZndwcmgwNFZEVGZhcW5QNTBxa3BmZEJLQWpmanEyCjFoZDZMd2hLeDRxSm9aelp2VkowV0lvR1ZLcjhJSjJOWGRTUVlUanZUZHhGczRTamdqNFFiaEVDZ1lFQTFBWUUKSEo3eVlza2EvS2V2OVVYbmVrSTRvMm5aYjJ1UVZXazRXSHlaY2NRN3VMQVhGY3lJcW5SZnoxczVzN3RMTzJCagozTFZNUVBzazFNY25oTTl4WE4vQ3ZDTys5b2t0RnNaMGJqWFh6NEJ5V2lFNHJPS1lhVEFwcDVsWlpUT3ZVMWNyCm05R3NwMWJoVDVZb2RaZ3IwUHQyYzR4U2krUVlEWnNFb2lFdzNkc0NnWUVBcVJLYWNweWZKSXlMZEJjZ0JycGkKQTRFalVLMWZsSjR3enNjbGFKUDVoM1NjZUFCejQzRU1YT0kvSXAwMFJsY3N6em83N3cyMmpud09mOEJSM0RBMwp6ZTRSWDIydWw4b0hGdldvdUZOTTNOZjNaNExuYXpVc0F0UGhNS2hRWGMrcEFBWGthUDJkZzZ0TU5PazFxaUNHCndvU212a1BVVE84b1ViRTB1NFZ4ZmZFQ2dZQUpPdDNROVNadUlIMFpSSitIV095enlOQTRaUEkvUkhwN0RXS1QKajVFS2Y5VnR1OVMxY1RyOTJLVVhITXlOUTNrSjg2OUZPMnMvWk85OGg5THptQ2hDTjhkOWN6enI5SnJPNUFMTApqWEtBcVFIUlpLTFgrK0ZRcXZVVlE3cTlpaHQyMEZPb3E5OE5SZDMzSGYxUzZUWDNHZ3RWQ21YSml6dDAxQ3ZHCmR4VnVnd0tCZ0M2Mlp0b0RLb3JyT2hvdTBPelprK2YwQS9rNDJBOENiL29VMGpwSzZtdmxEWmNYdUF1QVZTVXIKNXJCZjRVYmdVYndqa1ZWSFR6LzdDb1BWSjUvVUxJWk1Db1RUNFprNTZXWDk4ZE93Q3VTVFpZYnlBbDZNS1BBZApTZEpuVVIraEpnSVFDVGJ4K1dzYnh2d0FkbWErWUhtaVlPRzZhSklXMXdSd1VGOURLUEhHCi0tLS0tRU5EIFJTQSBQUklWQVRFIEtFWS0tLS0tCg==
-    ```
-
-2. In `kind: Secret` with `name: cattle-keys-server`, replace `<BASE64_CA>` with the base64 encoded string of the CA Certificate file (usually called `ca.pem` or `ca.crt`).
-
-    >**Note:**
-    > The base64 encoded string should be on the same line as `cacerts.pem`, without any newline at the beginning, in between or at the end.
-
-
-    **Step Result:** The file should look like the example below (the base64 encoded string should be different):
-
-    ```yaml
-    ---
-    apiVersion: v1
-    kind: Secret
-    metadata:
-      name: cattle-keys-server
-      namespace: cattle-system
-    type: Opaque
-    data:
-      cacerts.pem: LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUNvRENDQVlnQ0NRRHVVWjZuMEZWeU16QU5CZ2txaGtpRzl3MEJBUXNGQURBU01SQXdEZ1lEVlFRRERBZDAKWlhOMExXTmhNQjRYRFRFNE1EVXdOakl4TURRd09Wb1hEVEU0TURjd05USXhNRFF3T1Zvd0VqRVFNQTRHQTFVRQpBd3dIZEdWemRDMWpZVENDQVNJd0RRWUpLb1pJaHZjTkFRRUJCUUFEZ2dFUEFEQ0NBUW9DZ2dFQkFNQmpBS3dQCndhRUhwQTdaRW1iWWczaTNYNlppVmtGZFJGckJlTmFYTHFPL2R0RUdmWktqYUF0Wm45R1VsckQxZUlUS3UzVHgKOWlGVlV4Mmo1Z0tyWmpwWitCUnFiZ1BNbk5hS1hocmRTdDRtUUN0VFFZdGRYMVFZS0pUbWF5NU45N3FoNTZtWQprMllKRkpOWVhHWlJabkdMUXJQNk04VHZramF0ZnZOdmJ0WmtkY2orYlY3aWhXanp2d2theHRUVjZlUGxuM2p5CnJUeXBBTDliYnlVcHlad3E2MWQvb0Q4VUtwZ2lZM1dOWmN1YnNvSjhxWlRsTnN6UjVadEFJV0tjSE5ZbE93d2oKaG41RE1tSFpwZ0ZGNW14TU52akxPRUc0S0ZRU3laYlV2QzlZRUhLZTUxbGVxa1lmQmtBZWpPY002TnlWQUh1dApuay9DMHpXcGdENkIwbkVDQXdFQUFUQU5CZ2txaGtpRzl3MEJBUXNGQUFPQ0FRRUFHTCtaNkRzK2R4WTZsU2VBClZHSkMvdzE1bHJ2ZXdia1YxN3hvcmlyNEMxVURJSXB6YXdCdFJRSGdSWXVtblVqOGo4T0hFWUFDUEthR3BTVUsKRDVuVWdzV0pMUUV0TDA2eTh6M3A0MDBrSlZFZW9xZlVnYjQrK1JLRVJrWmowWXR3NEN0WHhwOVMzVkd4NmNOQQozZVlqRnRQd2hoYWVEQmdma1hXQWtISXFDcEsrN3RYem9pRGpXbi8walI2VDcrSGlaNEZjZ1AzYnd3K3NjUDIyCjlDQVZ1ZFg4TWpEQ1hTcll0Y0ZINllBanlCSTJjbDhoSkJqa2E3aERpVC9DaFlEZlFFVFZDM3crQjBDYjF1NWcKdE03Z2NGcUw4OVdhMnp5UzdNdXk5bEthUDBvTXl1Ty82Tm1wNjNsVnRHeEZKSFh4WTN6M0lycGxlbTNZQThpTwpmbmlYZXc9PQotLS0tLUVORCBDRVJUSUZJQ0FURS0tLS0tCg==
-    ```
-
-{{% /accordion %}}
-
-{{% accordion id="option-b" label="Option B—Bring Your Own Certificate: Signed by Recognized CA" %}}
->**Note:**
-> If you are using Self Signed Certificate, [click here](#option-a-bring-your-own-certificate-self-signed) to proceed.
-
-If you are using a Certificate Signed By A Recognized Certificate Authority, you will need to generate a base64 encoded string for the Certificate file and the Certificate Key file. Make sure that your certificate file includes all the [intermediate certificates](#cert-order) in the chain, the order of certificates in this case is first your own certificate, followed by the intermediates. Please refer to the documentation of your CSP (Certificate Service Provider) to see what intermediate certificate(s) need to be included.
-
-In the `kind: Secret` with `name: cattle-keys-ingress`:
-
-* Replace `<BASE64_CRT>` with the base64 encoded string of the Certificate file (usually called `cert.pem` or `domain.crt`)
-* Replace `<BASE64_KEY>` with the base64 encoded string of the Certificate Key file (usually called `key.pem` or `domain.key`)
-
-After replacing the values, the file should look like the example below (the base64 encoded strings should be different):
-
->**Note:**
-> The base64 encoded string should be on the same line as `tls.crt` or `tls.key`, without any newline at the beginning, in between or at the end.
-
-```yaml
---
-apiVersion: v1
-kind: Secret
-metadata:
-  name: cattle-keys-ingress
-  namespace: cattle-system
-type: Opaque
-data:
-  tls.crt: LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUM1RENDQWN5Z0F3SUJBZ0lKQUlHc25NeG1LeGxLTUEwR0NTcUdTSWIzRFFFQkN3VUFNQkl4RURBT0JnTlYKQkFNTUIzUmxjM1F0WTJFd0hoY05NVGd3TlRBMk1qRXdOREE1V2hjTk1UZ3dOekExTWpFd05EQTVXakFXTVJRdwpFZ1lEVlFRRERBdG9ZUzV5Ym1Ob2NpNXViRENDQVNJd0RRWUpLb1pJaHZjTkFRRUJCUUFEZ2dFUEFEQ0NBUW9DCmdnRUJBTFJlMXdzekZSb2Rib2pZV05DSHA3UkdJaUVIMENDZ1F2MmdMRXNkUUNKZlcrUFEvVjM0NnQ3bSs3TFEKZXJaV3ZZMWpuY2VuWU5JSGRBU0VnU0ducWExYnhUSU9FaE0zQXpib3B0WDhjSW1OSGZoQlZETGdiTEYzUk0xaQpPM1JLTGdIS2tYSTMxZndjbU9zWGUwaElYQnpUbmxnM20vUzlXL3NTc0l1dDVwNENDUWV3TWlpWFhuUElKb21lCmpkS3VjSHFnMTlzd0YvcGVUalZrcVpuMkJHazZRaWFpMU41bldRV0pjcThTenZxTTViZElDaWlwYU9hWWQ3RFEKYWRTejV5dlF0YkxQNW4wTXpnOU43S3pGcEpvUys5QWdkWDI5cmZqV2JSekp3RzM5R3dRemN6VWtLcnZEb05JaQo0UFJHc01yclFNVXFSYjRSajNQOEJodEMxWXNDQXdFQUFhTTVNRGN3Q1FZRFZSMFRCQUl3QURBTEJnTlZIUThFCkJBTUNCZUF3SFFZRFZSMGxCQll3RkFZSUt3WUJCUVVIQXdJR0NDc0dBUVVGQndNQk1BMEdDU3FHU0liM0RRRUIKQ3dVQUE0SUJBUUNKZm5PWlFLWkowTFliOGNWUW5Vdi9NZkRZVEJIQ0pZcGM4MmgzUGlXWElMQk1jWDhQRC93MgpoOUExNkE4NGNxODJuQXEvaFZYYy9JNG9yaFY5WW9jSEg5UlcvbGthTUQ2VEJVR0Q1U1k4S292MHpHQ1ROaDZ6Ci9wZTNqTC9uU0pYSjRtQm51czJheHFtWnIvM3hhaWpYZG9kMmd3eGVhTklvRjNLbHB2aGU3ZjRBNmpsQTM0MmkKVVlCZ09iN1F5KytRZWd4U1diSmdoSzg1MmUvUUhnU2FVSkN6NW1sNGc1WndnNnBTUXhySUhCNkcvREc4dElSYwprZDMxSk1qY25Fb1Rhc1Jyc1NwVmNGdXZyQXlXN2liakZyYzhienBNcE1obDVwYUZRcEZzMnIwaXpZekhwakFsCk5ZR2I2OHJHcjBwQkp3YU5DS2ErbCtLRTk4M3A3NDYwCi0tLS0tRU5EIENFUlRJRklDQVRFLS0tLS0K
-  tls.key: LS0tLS1CRUdJTiBSU0EgUFJJVkFURSBLRVktLS0tLQpNSUlFb3dJQkFBS0NBUUVBdEY3WEN6TVZHaDF1aU5oWTBJZW50RVlpSVFmUUlLQkMvYUFzU3gxQUlsOWI0OUQ5ClhmanEzdWI3c3RCNnRsYTlqV09keDZkZzBnZDBCSVNCSWFlcHJWdkZNZzRTRXpjRE51aW0xZnh3aVkwZCtFRlUKTXVCc3NYZEV6V0k3ZEVvdUFjcVJjamZWL0J5WTZ4ZDdTRWhjSE5PZVdEZWI5TDFiK3hLd2k2M21uZ0lKQjdBeQpLSmRlYzhnbWlaNk4wcTV3ZXFEWDJ6QVgrbDVPTldTcG1mWUVhVHBDSnFMVTNtZFpCWWx5cnhMTytvemx0MGdLCktLbG81cGgzc05CcDFMUG5LOUMxc3MvbWZRek9EMDNzck1Xa21oTDcwQ0IxZmIydCtOWnRITW5BYmYwYkJETnoKTlNRcXU4T2cwaUxnOUVhd3l1dEF4U3BGdmhHUGMvd0dHMExWaXdJREFRQUJBb0lCQUJKYUErOHp4MVhjNEw0egpwUFd5bDdHVDRTMFRLbTNuWUdtRnZudjJBZXg5WDFBU2wzVFVPckZyTnZpK2xYMnYzYUZoSFZDUEN4N1RlMDVxClhPa2JzZnZkZG5iZFQ2RjgyMnJleVByRXNINk9TUnBWSzBmeDVaMDQwVnRFUDJCWm04eTYyNG1QZk1vbDdya2MKcm9Kd09rOEVpUHZZekpsZUd0bTAwUm1sRysyL2c0aWJsOTVmQXpyc1MvcGUyS3ZoN2NBVEtIcVh6MjlpUmZpbApiTGhBamQwcEVSMjNYU0hHR1ZqRmF3amNJK1c2L2RtbDZURDhrSzFGaUtldmJKTlREeVNXQnpPbXRTYUp1K01JCm9iUnVWWG4yZVNoamVGM1BYcHZRMWRhNXdBa0dJQWxOWjRHTG5QU2ZwVmJyU0plU3RrTGNzdEJheVlJS3BWZVgKSVVTTHM0RUNnWUVBMmNnZUE2WHh0TXdFNU5QWlNWdGhzbXRiYi9YYmtsSTdrWHlsdk5zZjFPdXRYVzkybVJneQpHcEhUQ0VubDB0Z1p3T081T1FLNjdFT3JUdDBRWStxMDJzZndwcmgwNFZEVGZhcW5QNTBxa3BmZEJLQWpmanEyCjFoZDZMd2hLeDRxSm9aelp2VkowV0lvR1ZLcjhJSjJOWGRTUVlUanZUZHhGczRTamdqNFFiaEVDZ1lFQTFBWUUKSEo3eVlza2EvS2V2OVVYbmVrSTRvMm5aYjJ1UVZXazRXSHlaY2NRN3VMQVhGY3lJcW5SZnoxczVzN3RMTzJCagozTFZNUVBzazFNY25oTTl4WE4vQ3ZDTys5b2t0RnNaMGJqWFh6NEJ5V2lFNHJPS1lhVEFwcDVsWlpUT3ZVMWNyCm05R3NwMWJoVDVZb2RaZ3IwUHQyYzR4U2krUVlEWnNFb2lFdzNkc0NnWUVBcVJLYWNweWZKSXlMZEJjZ0JycGkKQTRFalVLMWZsSjR3enNjbGFKUDVoM1NjZUFCejQzRU1YT0kvSXAwMFJsY3N6em83N3cyMmpud09mOEJSM0RBMwp6ZTRSWDIydWw4b0hGdldvdUZOTTNOZjNaNExuYXpVc0F0UGhNS2hRWGMrcEFBWGthUDJkZzZ0TU5PazFxaUNHCndvU212a1BVVE84b1ViRTB1NFZ4ZmZFQ2dZQUpPdDNROVNadUlIMFpSSitIV095enlOQTRaUEkvUkhwN0RXS1QKajVFS2Y5VnR1OVMxY1RyOTJLVVhITXlOUTNrSjg2OUZPMnMvWk85OGg5THptQ2hDTjhkOWN6enI5SnJPNUFMTApqWEtBcVFIUlpLTFgrK0ZRcXZVVlE3cTlpaHQyMEZPb3E5OE5SZDMzSGYxUzZUWDNHZ3RWQ21YSml6dDAxQ3ZHCmR4VnVnd0tCZ0M2Mlp0b0RLb3JyT2hvdTBPelprK2YwQS9rNDJBOENiL29VMGpwSzZtdmxEWmNYdUF1QVZTVXIKNXJCZjRVYmdVYndqa1ZWSFR6LzdDb1BWSjUvVUxJWk1Db1RUNFprNTZXWDk4ZE93Q3VTVFpZYnlBbDZNS1BBZApTZEpuVVIraEpnSVFDVGJ4K1dzYnh2d0FkbWErWUhtaVlPRzZhSklXMXdSd1VGOURLUEhHCi0tLS0tRU5EIFJTQSBQUklWQVRFIEtFWS0tLS0tCg==
-```
-
-{{% /accordion %}}
-
-
-
-## 8. Configure FQDN
-
-There are two references to `<FQDN>` in the config file (one in this step and one in the next). Both need to be replaced with the FQDN chosen in [Configure DNS](#3-configure-dns).
-
-In the `kind: Ingress` with `name: cattle-ingress-http`:
-
-* Replace `<FQDN>` with the FQDN chosen in [Configure DNS](#3-configure-dns).
-
-After replacing `<FQDN>` with the FQDN chosen in [Configure DNS](#3-configure-dns), the file should look like the example below (`rancher.yourdomain.com` is the FQDN used in this example):
-
-```yaml
- ---
-  apiVersion: extensions/v1beta1
-  kind: Ingress
-  metadata:
-    namespace: cattle-system
-    name: cattle-ingress-http
-    annotations:
-      nginx.ingress.kubernetes.io/proxy-connect-timeout: "30"
-      nginx.ingress.kubernetes.io/proxy-read-timeout: "1800"   # Max time in seconds for ws to remain shell window open
-      nginx.ingress.kubernetes.io/proxy-send-timeout: "1800"   # Max time in seconds for ws to remain shell window open
-  spec:
-    rules:
-    - host: rancher.yourdomain.com
-      http:
-        paths:
-        - backend:
-            serviceName: cattle-service
-            servicePort: 80
-    tls:
-    - secretName: cattle-keys-ingress
-      hosts:
-      - rancher.yourdomain.com
-```
-
-Save the `.yml` file and close it.
-
-## 9. Configure Rancher version
-
-The last reference that needs to be replaced is `<RANCHER_VERSION>`. This needs to be replaced with a Rancher version which is marked as stable. The latest stable release of Rancher can be found in the [GitHub README](https://github.com/rancher/rancher/blob/master/README.md). Make sure the version is an actual version number, and not a named tag like `stable` or `latest`. The example below shows the version configured to `v2.0.6`.
-
-```
-      spec:
-        serviceAccountName: cattle-admin
-        containers:
-        - image: rancher/rancher:v2.0.6
-          imagePullPolicy: Always
-```
-
-## 10. Back Up Your RKE Config File
-
-After you close your `.yml` file, back it up to a secure location. You can use this file again when it's time to upgrade Rancher.
-
-## 11. Run RKE
-
-With all configuration in place, use RKE to launch Rancher. You can complete this action by running the `rke up` command and using the `--config` parameter to point toward your config file.
-
-1. From your workstation, make sure `rancher-cluster.yml` and the downloaded `rke` binary are in the same directory.
-
-2. Open a Terminal instance. Change to the directory that contains your config file and `rke`.
-
-3. Enter one of the `rke up` commands listen below.
-
-```
-rke up --config rancher-cluster.yml
-```
-
-**Step Result:** The output should be similar to the snippet below:
-
-```
-INFO[0000] Building Kubernetes cluster
-INFO[0000] [dialer] Setup tunnel for host [1.1.1.1]
-INFO[0000] [network] Deploying port listener containers
-INFO[0000] [network] Pulling image [alpine:latest] on host [1.1.1.1]
-...
-INFO[0101] Finished building Kubernetes cluster successfully
-```
-
-## 12. Back Up Auto-Generated Config File
-
-During installation, RKE automatically generates a config file named `kube_config_rancher-cluster.yml` in the same directory as the RKE binary. Copy this file and back it up to a safe location. You'll use this file later when upgrading Rancher Server.
-
-## What's Next?
-
-You have a couple of options:
-
- Create a backup of your Rancher Server in case of a disaster scenario: [High Availability Back Up and Restoration]({{<baseurl>}}/rancher/v2.x/en/installation/backups-and-restoration/ha-backup-and-restoration).
- Create a Kubernetes cluster: [Provisioning Kubernetes Clusters]({{<baseurl>}}/rancher/v2.x/en/cluster-provisioning/).
-
-<br/>
-
-## FAQ and Troubleshooting
-
-{{< ssl_faq_ha >}}
@@ -1,181 +0,0 @@
---
-title: Amazon NLB Configuration
-weight: 277
-aliases:
- /rancher/v2.x/en/installation/ha-server-install/nlb/
---
-
-> #### **Important: RKE add-on install is only supported up to Rancher v2.0.8**
->
->Please use the Rancher Helm chart to install Rancher on a Kubernetes cluster. For details, see the [Kubernetes Install - Installation Outline]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/#installation-outline).
->
->If you are currently using the RKE add-on install method, see [Migrating from a High-availability Kubernetes install with an RKE add-on]({{<baseurl>}}/rancher/v2.x/en/upgrades/upgrades/migrating-from-rke-add-on/) for details on how to move to using the helm chart.
-
-## Objectives
-
-Configuring an Amazon NLB is a multistage process. We've broken it down into multiple tasks so that it's easy to follow.
-
-1. [Create Target Groups](#create-target-groups)
-
-	Begin by creating two target groups for the **TCP** protocol, one regarding TCP port 443 and one regarding TCP port 80 (providing redirect to TCP port 443). You'll add your Linux nodes to these groups.
-
-2. [Register Targets](#register-targets)
-
-	Add your Linux nodes to the target groups.
-
-3. [Create Your NLB](#create-your-nlb)
-
-	Use Amazon's Wizard to create an Network Load Balancer. As part of this process, you'll add the target groups you created in **1. Create Target Groups**.
-
-
-## Create Target Groups
-
-Your first NLB configuration step is to create two target groups. Technically, only port 443 is needed to access Rancher, but its convenient to add a listener for port 80 which will be redirected to port 443 automatically. The NGINX controller on the nodes will make sure that port 80 gets redirected to port 443.
-
-Log into the [Amazon AWS Console](https://console.aws.amazon.com/ec2/) to get started, make sure to select the **Region** where your EC2 instances (Linux nodes) are created.
-
-The Target Groups configuration resides in the **Load Balancing** section of the **EC2** service. Select **Services** and choose **EC2**, find the section **Load Balancing** and open **Target Groups**.
-
-{{< img "/img/rancher/ha/nlb/ec2-loadbalancing.png" "EC2 Load Balancing section">}}
-
-Click **Create target group** to create the first target group, regarding TCP port 443.
-
-### Target Group (TCP port 443)
-
-Configure the first target group according to the table below. Screenshots of the configuration are shown just below the table.
-
-Option                                | Setting
--------------------------------------|------------------------------------
-Target Group Name                     | `rancher-tcp-443`
-Protocol                              | `TCP`
-Port                                  | `443`
-Target type                           | `instance`
-VPC                                   | Choose your VPC
-Protocol<br/>(Health Check)           | `HTTP`
-Path<br/>(Health Check)               | `/healthz`
-Port (Advanced health check)          | `override`,`80`
-Healthy threshold (Advanced health)   | `3`
-Unhealthy threshold (Advanced)        | `3`
-Timeout (Advanced)                    | `6 seconds`
-Interval (Advanced)                   | `10 second`
-Success codes                         | `200-399`
-
-<hr>
-**Screenshot Target group TCP port 443 settings**<br/>
-{{< img "/img/rancher/ha/nlb/create-targetgroup-443.png" "Target group 443">}}
-
-<hr>
-**Screenshot Target group TCP port 443 Advanced settings**<br/>
-{{< img "/img/rancher/ha/nlb/create-targetgroup-443-advanced.png" "Target group 443 Advanced">}}
-
-<hr>
-
-Click **Create target group** to create the second target group, regarding TCP port 80.
-
-### Target Group (TCP port 80)
-
-Configure the second target group according to the table below. Screenshots of the configuration are shown just below the table.
-
-Option                                | Setting
--------------------------------------|------------------------------------
-Target Group Name                     | `rancher-tcp-80`
-Protocol                              | `TCP`
-Port                                  | `80`
-Target type                           | `instance`
-VPC                                   | Choose your VPC
-Protocol<br/>(Health Check)           | `HTTP`
-Path<br/>(Health Check)               | `/healthz`
-Port (Advanced health check)          | `traffic port`
-Healthy threshold (Advanced health)   | `3`
-Unhealthy threshold (Advanced)        | `3`
-Timeout (Advanced)                    | `6 seconds`
-Interval (Advanced)                   | `10 second`
-Success codes                         | `200-399`
-
-<hr>
-**Screenshot Target group TCP port 80 settings**<br/>
-{{< img "/img/rancher/ha/nlb/create-targetgroup-80.png" "Target group 80">}}
-
-<hr>
-**Screenshot Target group TCP port 80 Advanced settings**<br/>
-{{< img "/img/rancher/ha/nlb/create-targetgroup-80-advanced.png" "Target group 80 Advanced">}}
-
-<hr>
-
-## Register Targets
-
-Next, add your Linux nodes to both target groups.
-
-Select the target group named **rancher-tcp-443**, click the tab **Targets** and choose **Edit**.
-
-{{< img "/img/rancher/ha/nlb/edit-targetgroup-443.png" "Edit target group 443">}}
-
-Select the instances (Linux nodes) you want to add, and click **Add to registered**.
-
-<hr>
-**Screenshot Add targets to target group TCP port 443**<br/>
-
-{{< img "/img/rancher/ha/nlb/add-targets-targetgroup-443.png" "Add targets to target group 443">}}
-
-<hr>
-**Screenshot Added targets to target group TCP port 443**<br/>
-
-{{< img "/img/rancher/ha/nlb/added-targets-targetgroup-443.png" "Added targets to target group 443">}}
-
-When the instances are added, click **Save** on the bottom right of the screen.
-
-Repeat those steps, replacing **rancher-tcp-443** with **rancher-tcp-80**. The same instances need to be added as targets to this target group.
-
-## Create Your NLB
-
-Use Amazon's Wizard to create an Network Load Balancer. As part of this process, you'll add the target groups you created in [Create Target Groups](#create-target-groups).
-
-1. From your web browser, navigate to the [Amazon EC2 Console](https://console.aws.amazon.com/ec2/).
-
-2. From the navigation pane, choose **LOAD BALANCING** > **Load Balancers**.
-
-3. Click **Create Load Balancer**.
-
-4. Choose **Network Load Balancer** and click **Create**.
-
-5. Complete the **Step 1: Configure Load Balancer** form.
-	- **Basic Configuration**
-
-	   - Name: `rancher`
-	   - Scheme: `internet-facing`
-	- **Listeners**
-
-		Add the **Load Balancer Protocols** and **Load Balancer Ports** below.
-		- `TCP`: `443`
-
-	- **Availability Zones**
-
-	   - Select Your **VPC** and **Availability Zones**.
-
-6. Complete the **Step 2: Configure Routing** form.
-
-	- From the **Target Group** drop-down, choose **Existing target group**.
-
-	- From the **Name** drop-down, choose `rancher-tcp-443`.
-
-	- Open **Advanced health check settings**, and configure **Interval** to `10 seconds`.
-
-7. Complete **Step 3: Register Targets**. Since you registered your targets earlier, all you have to do is click **Next: Review**.
-
-8. Complete **Step 4: Review**. Look over the load balancer details and click **Create** when you're satisfied.
-
-9. After AWS creates the NLB, click **Close**.
-
-## Add listener to NLB for TCP port 80
-
-1. Select your newly created NLB and select the **Listeners** tab.
-
-2. Click **Add listener**.
-
-3. Use `TCP`:`80` as **Protocol** : **Port**
-
-4. Click **Add action** and choose **Forward to...**
-
-5. From the **Forward to** drop-down, choose `rancher-tcp-80`.
-
-6. Click **Save** in the top right of the screen.
@@ -1,288 +0,0 @@
---
-title: Kubernetes Install with External Load Balancer (HTTPS/Layer 7)
-weight: 276
-aliases:
- /rancher/v2.x/en/installation/ha-server-install-external-lb/
---
-
-> #### **Important: RKE add-on install is only supported up to Rancher v2.0.8**
->
->Please use the Rancher Helm chart to install Rancher on a Kubernetes cluster. For details, see the [Kubernetes Install - Installation Outline]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/#installation-outline).
->
->If you are currently using the RKE add-on install method, see [Migrating from a Kubernetes Install with an RKE Add-on]({{<baseurl>}}/rancher/v2.x/en/upgrades/upgrades/migrating-from-rke-add-on/) for details on how to move to using the helm chart.
-
-This procedure walks you through setting up a 3-node cluster using the Rancher Kubernetes Engine (RKE). The cluster's sole purpose is running pods for Rancher. The setup is based on:
-
- Layer 7 Loadbalancer with SSL termination (HTTPS)
- [NGINX Ingress controller (HTTP)](https://kubernetes.github.io/ingress-nginx/)
-
-In an Kubernetes setup that uses a layer 7 load balancer, the load balancer accepts Rancher client connections over the HTTP protocol (i.e., the application level). This application-level access allows the load balancer to read client requests and then redirect to them to cluster nodes using logic that optimally distributes load.
-
-<sup>Kubernetes Rancher install with layer 7 load balancer, depicting SSL termination at load balancer</sup>
-![Rancher HA]({{<baseurl>}}/img/rancher/ha/rancher2ha-l7.svg)
-
-## Installation Outline
-
-Installation of Rancher in a high-availability configuration involves multiple procedures. Review this outline to learn about each procedure you need to complete.
-
-<!-- TOC -->
-
- [1. Provision Linux Hosts](#1-provision-linux-hosts)
- [2. Configure Load Balancer](#2-configure-load-balancer)
- [3. Configure DNS](#3-configure-dns)
- [4. Install RKE](#4-install-rke)
- [5. Download RKE Config File Template](#5-download-rke-config-file-template)
- [6. Configure Nodes](#6-configure-nodes)
- [7. Configure Certificates](#7-configure-certificates)
- [8. Configure FQDN](#8-configure-fqdn)
- [9. Configure Rancher version](#9-configure-rancher-version)
- [10. Back Up Your RKE Config File](#10-back-up-your-rke-config-file)
- [11. Run RKE](#11-run-rke)
- [12. Back Up Auto-Generated Config File](#12-back-up-auto-generated-config-file)
-
-
-<!-- /TOC -->
-## 1. Provision Linux Hosts
-
-Provision three Linux hosts according to our [Requirements]({{<baseurl>}}/rancher/v2.x/en/installation/requirements).
-
-## 2. Configure Load Balancer
-
-When using a load balancer in front of Rancher, there's no need for the container to redirect port communication from port 80 or port 443. By passing the header `X-Forwarded-Proto: https`, this redirect is disabled. This is the expected configuration when terminating SSL externally.
-
-The load balancer has to be configured to support the following:
-
-* **WebSocket** connections
-* **SPDY** / **HTTP/2** protocols
-* Passing / setting the following headers:
-
-| Header              | Value                                  | Description                                                                                                                                                              |
-|---------------------|----------------------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| `Host`              | FQDN used to reach Rancher. | To identify the server requested by the client.                                                                                                                           |
-| `X-Forwarded-Proto` | `https`                                | To identify the protocol that a client used to connect to the load balancer.<br /><br/>**Note:** If this header is present, `rancher/rancher` does not redirect HTTP to HTTPS. |
-| `X-Forwarded-Port`  | Port used to reach Rancher.             | To identify the protocol that client used to connect to the load balancer.                                                                                       |
-| `X-Forwarded-For`   | IP of the client connection.            | To identify the originating IP address of a client.                                                                                                                       |
-
-Health checks can be executed on the `/healthz` endpoint of the node, this will return HTTP 200.
-
-We have example configurations for the following load balancers:
-
-* [Amazon ALB configuration](alb/)
-* [NGINX configuration](nginx/)
-
-## 3. Configure DNS
-
-Choose a fully qualified domain name (FQDN) that you want to use to access Rancher (e.g., `rancher.yourdomain.com`).<br/><br/>
-
-1. Log into your DNS server a create a `DNS A` record that points to the IP address of your [load balancer](#2-configure-load-balancer).
-
-2. Validate that the `DNS A` is working correctly. Run the following command from any terminal, replacing `HOSTNAME.DOMAIN.COM` with your chosen FQDN:
-
-    `nslookup HOSTNAME.DOMAIN.COM`
-
-    **Step Result:** Terminal displays output similar to the following:
-
-    ```
-    $ nslookup rancher.yourdomain.com
-    Server:         YOUR_HOSTNAME_IP_ADDRESS
-    Address:        YOUR_HOSTNAME_IP_ADDRESS#53
-
-    Non-authoritative answer:
-    Name:   rancher.yourdomain.com
-    Address: HOSTNAME.DOMAIN.COM
-    ```
-
-<br/>
-
-## 4. Install RKE
-
-RKE (Rancher Kubernetes Engine) is a fast, versatile Kubernetes installer that you can use to install Kubernetes on your Linux hosts. We will use RKE to setup our cluster and run Rancher.
-
-1. Follow the [RKE Install]({{<baseurl>}}/rke/latest/en/installation) instructions.
-
-2. Confirm that RKE is now executable by running the following command:
-
-    ```
-    rke --version
-    ```
-
-## 5. Download RKE Config File Template
-
-RKE uses a YAML config file to install and configure your Kubernetes cluster. There are 2 templates to choose from, depending on the SSL certificate you want to use.
-
-1. Download one of following templates, depending on the SSL certificate you're using.
-
-	- [Template for self-signed certificate<br/> `3-node-externalssl-certificate.yml`]({{<baseurl>}}/rancher/v2.x/en/installation/options/cluster-yml-templates/3-node-externalssl-certificate)
-	- [Template for certificate signed by recognized CA<br/> `3-node-externalssl-recognizedca.yml`]({{<baseurl>}}/rancher/v2.x/en/installation/options/cluster-yml-templates/3-node-externalssl-recognizedca)
-
-    >**Advanced Config Options:**
-    >
-    >- Want records of all transactions with the Rancher API? Enable the [API Auditing]({{<baseurl>}}/rancher/v2.x/en/installation/api-auditing) feature by editing your RKE config file. For more information, see how to enable it in [your RKE config file]({{<baseurl>}}/rancher/v2.x/en/installation/options/helm2/rke-add-on/api-auditing/).
-    >- Want to know the other config options available for your RKE template? See the [RKE Documentation: Config Options]({{<baseurl>}}/rke/latest/en/config-options/).
-
-
-2. Rename the file to `rancher-cluster.yml`.
-
-## 6. Configure Nodes
-
-Once you have the `rancher-cluster.yml` config file template, edit the nodes section to point toward your Linux hosts.
-
-1. Open `rancher-cluster.yml` in your favorite text editor.
-
-1. Update the `nodes` section with the information of your [Linux hosts](#1-provision-linux-hosts).
-
-    For each node in your cluster, update the following placeholders: `IP_ADDRESS_X` and `USER`. The specified user should be able to access the Docket socket, you can test this by logging in with the specified user and run `docker ps`.
-
-    >**Note:**
-    >
-    >When using RHEL/CentOS, the SSH user can't be root due to https://bugzilla.redhat.com/show_bug.cgi?id=1527565. See [Operating System Requirements]({{<baseurl>}}/rke/latest/en/installation/os#redhat-enterprise-linux-rhel-centos) for RHEL/CentOS specific requirements.
-
-        nodes:
-            # The IP address or hostname of the node
-        - address: IP_ADDRESS_1
-            # User that can login to the node and has access to the Docker socket (i.e. can execute `docker ps` on the node)
-            # When using RHEL/CentOS, this can't be root due to https://bugzilla.redhat.com/show_bug.cgi?id=1527565
-            user: USER
-            role: [controlplane,etcd,worker]
-            # Path the SSH key that can be used to access to node with the specified user
-            ssh_key_path: ~/.ssh/id_rsa
-        - address: IP_ADDRESS_2
-            user: USER
-            role: [controlplane,etcd,worker]
-            ssh_key_path: ~/.ssh/id_rsa
-        - address: IP_ADDRESS_3
-            user: USER
-            role: [controlplane,etcd,worker]
-            ssh_key_path: ~/.ssh/id_rsa
-
-1. **Optional:** By default, `rancher-cluster.yml` is configured to take backup snapshots of your data. To disable these snapshots, change the `backup` directive setting to `false`, as depicted below.
-
-        services:
-          etcd:
-            backup: false
-
-## 7. Configure Certificates
-
-For security purposes, SSL (Secure Sockets Layer) is required when using Rancher. SSL secures all Rancher network communication, like when you login or interact with a cluster.
-
-Choose from the following options:
-
-{{% accordion id="option-a" label="Option A—Bring Your Own Certificate: Self-Signed" %}}
->**Prerequisites:**
->Create a self-signed certificate.
->
->- The certificate files must be in [PEM format](#pem).
->- The certificate files must be encoded in [base64](#base64).
->- In your certificate file, include all intermediate certificates in the chain. Order your certificates with your certificate first, followed by the intermediates. For an example, see [SSL FAQ / Troubleshooting](#cert-order).
-
-In `kind: Secret` with `name: cattle-keys-ingress`, replace `<BASE64_CA>` with the base64 encoded string of the CA Certificate file (usually called `ca.pem` or `ca.crt`)
-
->**Note:** The base64 encoded string should be on the same line as `cacerts.pem`, without any newline at the beginning, in between or at the end.
-
-After replacing the values, the file should look like the example below (the base64 encoded strings should be different):
-
-        ---
-        apiVersion: v1
-        kind: Secret
-        metadata:
-            name: cattle-keys-server
-            namespace: cattle-system
-        type: Opaque
-        data:
-            cacerts.pem: LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUNvRENDQVlnQ0NRRHVVWjZuMEZWeU16QU5CZ2txaGtpRzl3MEJBUXNGQURBU01SQXdEZ1lEVlFRRERBZDAKWlhOMExXTmhNQjRYRFRFNE1EVXdOakl4TURRd09Wb1hEVEU0TURjd05USXhNRFF3T1Zvd0VqRVFNQTRHQTFVRQpBd3dIZEdWemRDMWpZVENDQVNJd0RRWUpLb1pJaHZjTkFRRUJCUUFEZ2dFUEFEQ0NBUW9DZ2dFQkFNQmpBS3dQCndhRUhwQTdaRW1iWWczaTNYNlppVmtGZFJGckJlTmFYTHFPL2R0RUdmWktqYUF0Wm45R1VsckQxZUlUS3UzVHgKOWlGVlV4Mmo1Z0tyWmpwWitCUnFiZ1BNbk5hS1hocmRTdDRtUUN0VFFZdGRYMVFZS0pUbWF5NU45N3FoNTZtWQprMllKRkpOWVhHWlJabkdMUXJQNk04VHZramF0ZnZOdmJ0WmtkY2orYlY3aWhXanp2d2theHRUVjZlUGxuM2p5CnJUeXBBTDliYnlVcHlad3E2MWQvb0Q4VUtwZ2lZM1dOWmN1YnNvSjhxWlRsTnN6UjVadEFJV0tjSE5ZbE93d2oKaG41RE1tSFpwZ0ZGNW14TU52akxPRUc0S0ZRU3laYlV2QzlZRUhLZTUxbGVxa1lmQmtBZWpPY002TnlWQUh1dApuay9DMHpXcGdENkIwbkVDQXdFQUFUQU5CZ2txaGtpRzl3MEJBUXNGQUFPQ0FRRUFHTCtaNkRzK2R4WTZsU2VBClZHSkMvdzE1bHJ2ZXdia1YxN3hvcmlyNEMxVURJSXB6YXdCdFJRSGdSWXVtblVqOGo4T0hFWUFDUEthR3BTVUsKRDVuVWdzV0pMUUV0TDA2eTh6M3A0MDBrSlZFZW9xZlVnYjQrK1JLRVJrWmowWXR3NEN0WHhwOVMzVkd4NmNOQQozZVlqRnRQd2hoYWVEQmdma1hXQWtISXFDcEsrN3RYem9pRGpXbi8walI2VDcrSGlaNEZjZ1AzYnd3K3NjUDIyCjlDQVZ1ZFg4TWpEQ1hTcll0Y0ZINllBanlCSTJjbDhoSkJqa2E3aERpVC9DaFlEZlFFVFZDM3crQjBDYjF1NWcKdE03Z2NGcUw4OVdhMnp5UzdNdXk5bEthUDBvTXl1Ty82Tm1wNjNsVnRHeEZKSFh4WTN6M0lycGxlbTNZQThpTwpmbmlYZXc9PQotLS0tLUVORCBDRVJUSUZJQ0FURS0tLS0tCg==
-
-{{% /accordion %}}
-{{% accordion id="option-b" label="Option B—Bring Your Own Certificate: Signed by Recognized CA" %}}
-If you are using a Certificate Signed By A Recognized Certificate Authority, you don't need to perform any step in this part.
-{{% /accordion %}}
-
-## 8. Configure FQDN
-
-There is one reference to `<FQDN>` in the RKE config file. Replace this reference with the FQDN you chose in [3. Configure DNS](#3-configure-dns).
-
-1. Open `rancher-cluster.yml`.
-
-2. In the `kind: Ingress` with `name: cattle-ingress-http:`
-
-    Replace `<FQDN>` with the FQDN chosen in [3. Configure DNS](#3-configure-dns).
-
-    **Step Result:** After replacing the values, the file should look like the example below (the base64 encoded strings should be different):
-
-    ```
-    apiVersion: extensions/v1beta1
-      kind: Ingress
-      metadata:
-        namespace: cattle-system
-        name: cattle-ingress-http
-        annotations:
-          nginx.ingress.kubernetes.io/proxy-connect-timeout: "30"
-          nginx.ingress.kubernetes.io/proxy-read-timeout: "1800"   # Max time in seconds for ws to remain shell window open
-          nginx.ingress.kubernetes.io/proxy-send-timeout: "1800"   # Max time in seconds for ws to remain shell window open
-      spec:
-        rules:
-        - host: rancher.yourdomain.com
-          http:
-            paths:
-            - backend:
-                serviceName: cattle-service
-                servicePort: 80
-    ```
-
-
-3. Save the file and close it.
-
-## 9. Configure Rancher version
-
-The last reference that needs to be replaced is `<RANCHER_VERSION>`. This needs to be replaced with a Rancher version which is marked as stable. The latest stable release of Rancher can be found in the [GitHub README](https://github.com/rancher/rancher/blob/master/README.md). Make sure the version is an actual version number, and not a named tag like `stable` or `latest`. The example below shows the version configured to `v2.0.6`.
-
-```
-      spec:
-        serviceAccountName: cattle-admin
-        containers:
-        - image: rancher/rancher:v2.0.6
-          imagePullPolicy: Always
-```
-
-## 10. Back Up Your RKE Config File
-
-After you close your RKE config file, `rancher-cluster.yml`, back it up to a secure location. You can use this file again when it's time to upgrade Rancher.
-
-## 11. Run RKE
-
-With all configuration in place, use RKE to launch Rancher. You can complete this action by running the `rke up` command and using the `--config` parameter to point toward your config file.
-
-1. From your workstation, make sure `rancher-cluster.yml` and the downloaded `rke` binary are in the same directory.
-
-2. Open a Terminal instance. Change to the directory that contains your config file and `rke`.
-
-3. Enter one of the `rke up` commands listen below.
-
-    ```
-    rke up --config rancher-cluster.yml
-    ```
-
-    **Step Result:** The output should be similar to the snippet below:
-
-    ```
-    INFO[0000] Building Kubernetes cluster
-    INFO[0000] [dialer] Setup tunnel for host [1.1.1.1]
-    INFO[0000] [network] Deploying port listener containers
-    INFO[0000] [network] Pulling image [alpine:latest] on host [1.1.1.1]
-    ...
-    INFO[0101] Finished building Kubernetes cluster successfully
-    ```
-
-## 12. Back Up Auto-Generated Config File
-
-During installation, RKE automatically generates a config file named `kube_config_rancher-cluster.yml` in the same directory as the `rancher-cluster.yml` file. Copy this file and back it up to a safe location. You'll use this file later when upgrading Rancher Server.
-
-## What's Next?
-
- **Recommended:** Review [Creating Backups—High Availability Back Up and Restoration]({{<baseurl>}}/rancher/v2.x/en/backups/backups/ha-backups/) to learn how to backup your Rancher Server in case of a disaster scenario.
- Create a Kubernetes cluster: [Creating a Cluster]({{<baseurl>}}/rancher/v2.x/en/tasks/clusters/creating-a-cluster/).
-
-<br/>
-
-## FAQ and Troubleshooting
-
-{{< ssl_faq_ha >}}
--- a/Show More
+++ b/Show More