add back in rke based install, align to outline.

2026-09-26 04:58:07 +00:00 · 2018-07-16 10:03:03 +10:00
parent 0456a27c5a
commit c3b59721ac
26 changed files with 1542 additions and 36 deletions
@@ -10,28 +10,16 @@ This section contains instructions for installing Rancher in development and pro

 	Install Rancher on a single Linux host.

- [Single Node Installation with External Load Balancer](single-node-install-external-lb/)
-
-	In this scenario, you install Rancher on a single Linux host and access it using an external load balancer/proxy.
-
 -  [High Availability Installation](ha-server-install/)

 	This install scenario creates a new Kubernetes cluster dedicated to running Rancher Server in a high-availability (HA) configuration.

-### Advanced Install Scenarios
+### Reference

-  [Air Gap Installation](air-gap-installation/)
+-  [Images required for Air Gap Installation](air-gap-images/)

 	Required images and configuration to install Rancher Server in an environment without direct Internet access.

-  [Rancher HTTP Proxy Configuration](proxy-configuration/)
-
-	Rancher configuration to run behind a proxy.
-
-
-### Reference
-
 -  [Port Requirements](references/)

 	List of required ports you must open to operate Rancher.
-
@@ -29,7 +29,7 @@ The following CLI tools are required for this install. Please make sure these to

 ## Installation Outline

-1. [Create Nodes and Load Balancer]({{< baseurl >}}/rancher/v2.x/en/installation/ha-server-install2/create-nodes-and-load-balancer/)
-1. [Install Kubernetes with RKE]({{< baseurl >}}/rancher/v2.x/en/installation/ha-server-install2/rke/)
-1. [Initialize Helm (tiller)]({{< baseurl >}}/rancher/v2.x/en/installation/ha-server-install2/helm/)
-1. [Install Rancher]({{< baseurl >}}/rancher/v2.x/en/installation/ha-server-install2/rancher/)
+1. [Create Nodes and Load Balancer](create-nodes-and-load-balancer/)
+1. [Install Kubernetes with RKE](install-kubernetese-rke/)
+1. [Initialize Helm (tiller)](helm-install/)
+1. [Install Rancher](rancher-install/)
@@ -1,6 +1,6 @@
 ---
 title: 1 - Create Nodes and Load Balancer
-weight: 276
+weight: 185
 ---

 Use your provider of choice to provision 3 nodes and a Load Balancer endpoint for your RKE install.
@@ -54,7 +54,7 @@ In addition to the ports listed above these ports must be open between nodes.

 ### Load Balancer

-RKE will configure an Ingress-Controller pod, on each of your nodes. The ingress controller pods are bound to ports 80 and 443 tcp on the host network and are the entry point for https traffic to the Rancher server.
+RKE will configure an ingress-controller pod, on each of your nodes. The ingress-controller pods are bound to ports 80 and 443 tcp 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.

@@ -64,4 +64,4 @@ Configure a load balancer as a basic Layer 4 tcp forwarder. The exact configurat

 <br/>

-### [Next: Install Kubernetes with RKE](../rke/)
+### [Next: Install Kubernetes with RKE](../install-kubernetes-rke/)
@@ -1,6 +1,6 @@
 ---
 title: 3 - Initialize Helm (Install tiller)
-weight: 276
+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/)
@@ -65,4 +65,4 @@ helm init --service-account tiller

 > 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.

-### [Next: Install Rancher](../rancher/)
+### [Next: Install Rancher](../rancher-install/)
@@ -1,13 +1,13 @@
 ---
 title: 2 - Install Kubernetes with RKE
-weight: 276
+weight: 190
 ---

-Configure the RKE `cluster.yml` and run `rke` to install Kubernetes with a HA `etcd` install.
+Configure the RKE `rancher-cluster.yml` and run `rke` to install Kubernetes with a HA `etcd` install.

-### Create a `cluster.yml` File
+### Create a `rancher-cluster.yml` File

-Using the sample below create a `cluster.yml` file. Replace the IP Addresses in the `nodes` list with the IP address or DNS names of the 3 Nodes you created.
+Using the sample below create a `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.

 ```yaml
 nodes:
@@ -49,17 +49,17 @@ Please see the [RKE Documentation]({{< baseurl >}}/rke/v0.1.x/en/) for the full
 ### Run RKE

 ```
-rke up --config ./cluster.yaml
+rke up --config ./rancher-cluster.yaml
 ```

 ### Testing your cluster

-`rke` should have created a file `kube_config_cluster.yml`. This file has the credentials for `kubectl` and `helm`.
+`rke` should have created a file `kube_config_rancher-cluster.yml`. This file has the credentials for `kubectl` and `helm`.

-You can copy this file to `$HOME/.kube/config` or if you are working with multiple Kubernetes clusters, set`KUBECONFIG` environmental variable to the path of `kube_config_cluster.yml`.
+You can copy this file to `$HOME/.kube/config` or if you are working with multiple Kubernetes clusters, set`KUBECONFIG` environmental variable to the path of `kube_config_rancher-cluster.yml`.

 ```
-export KUBECONFIG=$(pwd)/kube_config_cluster.yml
+export KUBECONFIG=$(pwd)/kube_config_rancher-cluster.yml
 ```

 Test you connectivity with `kubectl` and see if you can get the list of nodes back.
@@ -73,6 +73,12 @@ NAME                          STATUS    ROLES                      AGE       VER
 165.227.127.226               Ready     controlplane,etcd,worker   11m       v1.10.1
 ```

-Issues or errors?  See the [Troubleshooting](troubleshooting/) page.
+### Save your files

-### [Next: Initialize Helm](../helm/)
+You will need to save a copy of the `kube_config_rancher-cluster.yml` and `rancher-cluster.yml` files. You will need these files to maintain and upgrade your Rancher instance.
+
+### Issues or errors?
+
+See the [Troubleshooting](troubleshooting/) page.
+
+### [Next: Initialize Helm](../helm-install/)
@@ -0,0 +1,56 @@
+---
+title: Migrating from RKE All-In-One Install
+weight: 235
+---
+
+The following instructions will help guide you through migrating from the RKE All-In-One install to managing Rancher with the Helm package manager.
+
+You will need the to have [kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/#install-kubectl) installed and `kube_config_rancher-cluster.yml` credentials file generated by RKE.
+
+> NOTE: This guide assumes a standard Rancher install. If you have modified any of the object names or namespaces, please adjust accordingly.
+
+### Point kubectl at your Rancher Cluster
+
+Make sure `kubectl` is using the correct cluster.  Export the `KUBECONFIG` environmental variable pointing at the `kube_config_rancher-cluster.yml`
+
+```
+export KUBECONFIG=$(pwd)/kube_config_rancher-cluster.yml
+```
+
+### Save your certificates
+
+If you have terminated ssl on the Rancher cluster ingress, recover your certificate and key for use in the Helm install.
+
+Use `kubectl` to get the secret, decode the value and direct the output to a file.
+
+```
+kubectl -n cattle-system get secret cattle-keys-ingress -o jsonpath --template='{ .data.tls\.crt }' | base64 -d > tls.crt
+kubectl -n cattle-system get secret cattle-keys-ingress -o jsonpath --template='{ .data.tls\.key }' | base64 -d > tls.key
+```
+
+If you specified a private CA root cert
+
+```
+kubectl -n cattle-system get secret cattle-keys-server -o jsonpath --template='{ .data.cacerts\.pem }' | base64 -d > tls.crt
+```
+
+### Remove previous Kubernetes objects
+
+Remove the kubernetes objects created by the RKE install.
+
+> NOTE: Removing these Kubernetes components will not affect the Rancher configuration or database, but with any maintenance it is a good idea to create a backup of the data before hand. See [Creating Backups-HA Install]({{< baseurl >}}/rancher/v2.x/en/backups/ha-backups) for details.
+
+```
+kubectl -n cattle-system delete ingress cattle-ingress-http
+kubectl -n cattle-system delete service cattle-service
+kubectl -n cattle-system delete deployment cattle
+kubectl -n cattle-system delete clusterrolebinding cattle-crb
+kubectl -n cattle-system delete serviceaccount cattle-admin
+```
+
+### Follow Helm and Rancher install steps
+
+From here follow the standard install steps.
+
+* [3 - Initialize Helm (Install tiller)](../3-helm-install/)
+* [4 - Install Rancher](../4-rancher-install/)
@@ -1,11 +1,10 @@
 ---
 title: 4 - Install Rancher
-weight: 276
+weight: 200
 ---

 Rancher installation is now managed using the Helm package manager for Kubernetes.  Use `helm` to install the prerequisite and Rancher charts.

-
 ### Add the Chart Repo

 Use `helm repo add` to add the Rancher chart repository.
@@ -24,6 +24,7 @@ weight: 276
 | `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` - Where to terminate SSL. - "ingress, external"

 <br/>

@@ -50,4 +51,25 @@ Add the `rancherImage` to point to your private registry image and `imagePullSec
 ```
 --set rancherImage=reg.example.com:5000/rancher/rancher \
 --set imagePullSecrets[0].name=regcred
-```
+```
+
+### External TLS Termination
+
+If you wish to terminate the SSL/TLS on a load-balancer external to the Rancher cluster (ingress), use the `--tls=external` option and point your load balancer at port http 80.
+
+> NOTE: If you are using a Private CA signed cert, add `--set privateCA=true` and see [Adding TLS Secrets - Private CA Signed - Additional Steps](../tls-secrets/#private-ca-signed---additional-steps) 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.
+
+> NOTE: The `tls=external` option will expose the Rancher interface on http port 80.  Clients that are allowed to connect directly to the Rancher cluster will not be encrypted. We recommend that you restrict direct access at the network level to just your load balancer.
+
+#### Required headers
+
+* `Host`
+* `X-Forwarded-Proto`
+* `X-Forwarded-Port`
+* `X-Forwarded-For`
+
+#### Health checks
+
+Rancher will respond `200` to health checks on the `/healthz` endpoint.
@@ -0,0 +1,10 @@
+---
+title: RKE All-In-One Install
+weight: 276
+---
+
+Rancher can be installed by providing the appropriate Kubernetes manifest configurations to RKE's `addons` feature. See the following instructions for examples appropriate to your environment.
+
+* [High Availability Installation with External Load Balancer (TCP/Layer 4)](./ha-server-install/)
+* [High Availability Installation with External Load Balancer (HTTPS/Layer 7)](./ha-server-install-external-lb)
+* [Troubleshooting RKE All-In-One Installs](./troubleshooting-ha)
@@ -0,0 +1,337 @@
+---
+title: High Availability Installation with External Load Balancer (HTTPS/Layer 7)
+weight: 276
+---
+This set of instructions creates a new Kubernetes cluster that's dedicated to running Rancher in a high-availability (HA) configuration. 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)
+
+![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.
+
+1. [Provision Linux Hosts](#1-provision-linux-hosts)
+
+	Provision three Linux hosts to serve as your Kubernetes cluster.
+
+2. [Configure Load Balancer](#2-configure-load-balancer)
+
+	Configure your load balancer to have a highly available single point of entry to your Rancher cluster.
+
+3. [Configure DNS](#3-configure-dns)
+
+	Make your setup accessible using a DNS name by configuring the DNS to point to your loadbalancer.
+
+4. [Download RKE](#4-download-rke)
+
+	[RKE](https://github.com/rancher/rke/releases) is a fast, versatile Kubernetes installer that you can use to install Kubernetes on your Linux hosts.
+
+5. [Download RKE Config File Template](#5-download-config-file-template)
+
+	RKE uses a YAML config file to install and configure your Kubernetes cluster. Download one of our RKE config file templates to get started.
+
+6. [Configure Nodes](#6-configure-nodes)
+
+	Configure the **Nodes** section of the RKE config template.
+
+7. [Configure Certificates](#7-configure-certificates)
+
+	Configure the **Certificates** part of the template too.
+
+8. [Configure FQDN](#8-configure-fqdn)
+
+	And the **FQDN** part.
+
+9. [Back Up Your RKE Config File](#9-back-up-your-rke-config-file)
+
+	After you've completed configuration of the RKE config file: 1. it's no longer a template since you'll be using it, and 2. you should back up the RKE config file to a safe place. You will reuse this file for upgrades later.
+
+10. [Run RKE](#10-run-rke)
+
+	Run RKE to deploy Rancher to your cluster.
+
+11. [Back Up Auto-Generated Config File](#11-back-up-auto-generated-config-file)
+
+	During installation, RKE generates a config file that you'll use later for upgrades. Back it up to a safe location.
+
+<br/>
+## 1. Provision Linux Hosts
+
+Before you install Rancher, confirm you meet the host requirements. Provision 3 new Linux hosts using the requirements below.
+
+### Requirements
+
+#### Operating System 
+
+{{< requirements_os >}}
+
+#### Hardware 
+
+{{< requirements_hardware >}}
+
+#### Software 
+
+{{< requirements_software >}}
+
+{{< note_server-tags >}}
+
+#### Ports
+
+The following diagram depicts the basic port requirements for Rancher. For a comprehensive list, see [Port Requirements]({{< baseurl >}}/rancher/v2.x/en/installation/references/).
+
+![Basic Port Requirements]({{< baseurl >}}/img/rancher/port-communications.png)
+
+## 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]({{< baseurl >}}/rancher/v2.x/en/installation/ha-server-install-external-lb/alb)
+* [NGINX configuration]({{< baseurl >}}/rancher/v2.x/en/installation/ha-server-install-external-lb/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. Download RKE
+
+RKE is a fast, versatile Kubernetes installer that you can use to install Kubernetes on your Linux hosts. We will be using RKE to setup our cluster and run Rancher.
+
+1. From your workstation, open a web browser and navigate to our [RKE Releases](https://github.com/rancher/rke/releases/latest) page. Download the latest RKE installer applicable to your Operating System:
+
+    - **MacOS**: `rke_darwin-amd64`
+    - **Linux**: `rke_linux-amd64`
+    - **Windows**: `rke_windows-amd64.exe`
+
+2. Make the RKE binary that you just downloaded executable. Open Terminal, change directory to the location of the RKE binary, and then run one of the commands below.
+
+    >**Using Windows?**
+    >The file is already an executable. Skip to [Download Config File Template](#5-download-config-file-template).
+
+    ```
+    # MacOS
+    $ chmod +x rke_darwin-amd64
+    # Linux
+    $ chmod +x rke_linux-amd64
+    ```
+
+3.  Confirm that RKE is now executable by running the following command:
+
+    ```
+    # MacOS
+    $ ./rke_darwin-amd64 --version
+    # Linux
+    $ ./rke_linux-amd64 --version
+    ```
+
+    **Step Result:** You receive output similar to what follows:
+    ```
+    rke version v<N.N.N>
+    ```
+
+## 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`](https://raw.githubusercontent.com/rancher/rancher/58e695b51096b1f404188379cea6f6a35aea9e4c/rke-templates/3-node-externalssl-certificate.yml)
+	- [Template for certificate signed by recognized CA<br/> `3-node-externalssl-recognizedca.yml`](https://raw.githubusercontent.com/rancher/rancher/7f60dc3afe1b45287ac36ba6bde6f7c6e35c11fe/rke-templates/3-node-externalssl-recognizedca.yml)
+
+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.
+
+2. Update the `nodes` section with the information of your [Linux hosts](#provision-linux-hosts).
+
+    For each node in your cluster, update the following placeholders: `IP_ADDRESS_X` and `USER`.
+
+```
+nodes:
+  - address: IP_ADDRESS_1
+    # THE IP ADDRESS OR HOSTNAME OF THE NODE
+	user: USER
+    # USER WITH ADMIN ACCESS. USUALLY `root`
+	role: [controlplane,etcd,worker]
+	ssh_key_path: ~/.ssh/id_rsa
+    # PATH TO SSH KEY THAT AUTHENTICATES ON YOUR WORKSTATION
+    # USUALLY THE VALUE ABOVE
+  - 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
+```
+
+## 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:
+
+- [Option A—Bring Your Own Certificate: Self-Signed](#option-a-bring-your-own-certificate-self-signed)
+- [Option B—Bring Your Own Certificate: Signed by Recognized CA](#option-b-bring-your-own-certificate-signed-by-recognized-ca)
+
+### 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).
+
+1. 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.
+
+    **Result:** 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==
+    ```
+
+### 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.
+
+## 8. Configure FQDN
+
+There is one reference to `<FQDN>` in the RKE config file. Replace this reference with the FQDN you chose in in [3. Configure DNS](#part-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. 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.
+
+## 10. 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.
+
+    ```
+    # MacOS
+    ./rke_darwin-amd64 up --config rancher-cluster.yml
+    # Linux
+    ./rke_linux-amd64 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
+    ```
+
+## 11. 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?
+
+You have a couple of options:
+
+- Create a backup of your Rancher Server in case of a disaster scenario: [High Availablility Back Up and Restoration]({{< baseurl >}}/rancher/v2.x/en/installation/backups-and-restoration/ha-backup-and-restoration).
+- Create a Kubernetes cluster: [Creating a Cluster]({{< baseurl >}}/rancher/v2.x/en/tasks/clusters/creating-a-cluster/).
+
+<br/>
+
+## FAQ and Troubleshooting
+
+{{< ssl_faq_ha >}}
@@ -0,0 +1,94 @@
+---
+title: Amazon ALB configuration
+weight: 277
+---
+## Objectives
+
+Configuring an Amazon ALB is a multistage process. We've broken it down into multiple tasks so that it's easy to follow.
+
+1. [Create Target Group](#create-target-group)
+
+	Begin by creating one target group for the http protocol. You'll add your Linux nodes to this group.
+
+2. [Register Targets](#register-targets)
+
+	Add your Linux nodes to the target group.
+
+3. [Create Your ALB](#create-your-alb)
+
+	Use Amazon's Wizard to create an Application Load Balancer. As part of this process, you'll add the target groups you created in **1. Create Target Groups**.
+
+
+## Create Target Group
+
+Your first ALB configuration step is to create one target group for HTTP.
+
+Log into the [Amazon AWS Console](https://console.aws.amazon.com/ec2/) to get started.
+
+The document below will guide you through this process. Use the data in the tables below to complete the procedure.
+
+[Amazon Documentation: Create a Target Group](https://docs.aws.amazon.com/elasticloadbalancing/latest/application/create-target-group.html)
+
+### Target Group (HTTP)
+
+Option                      | Setting
+----------------------------|------------------------------------
+Target Group Name           | `rancher-http-80`
+Protocol                    | `HTTP`
+Port                        | `80`
+Target type                 | `instance`
+VPC                         | Choose your VPC
+Protocol<br/>(Health Check) | `HTTP`
+Path<br/>(Health Check)     | `/healthz`
+
+## Register Targets
+
+Next, add your Linux nodes to your target group.
+
+[Amazon Documentation: Register Targets with Your Target Group](https://docs.aws.amazon.com/elasticloadbalancing/latest/application/target-group-register-targets.html)
+
+### Create Your ALB
+
+Use Amazon's Wizard to create an Application Load Balancer. As part of this process, you'll add the target group you created in [Create Target Group](#create-target-group).
+
+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 **Application Load Balancer**.
+
+5. Complete the **Step 1: Configure Load Balancer** form.
+	- **Basic Configuration**
+
+	   - Name: `rancher-http`
+	   - Scheme: `internet-facing`
+	   - IP address type: `ipv4`
+	- **Listeners**
+
+		Add the **Load Balancer Protocols** and **Load Balancer Ports** below.
+		- `HTTP`: `80`
+		- `HTTPS`: `443`
+
+	- **Availability Zones**
+
+	   - Select Your **VPC** and **Availability Zones**.
+
+6. Complete the **Step 2: Configure Security Settings** form.
+
+	Configure the certificate you want to use for SSL termination.
+
+7. Complete the **Step 3: Configure Security Groups** form.
+
+8. Complete the **Step 4: Configure Routing** form.
+
+	- From the **Target Group** drop-down, choose **Existing target group**.
+
+	- Add target group `rancher-http-80`.
+
+9. Complete **Step 5: Register Targets**. Since you registered your targets earlier, all you have to do it click **Next: Review**.
+
+10. Complete **Step 6: Review**. Look over the load balancer details and click **Create** when you're satisfied.
+
+11. After AWS creates the ALB, click **Close**.
@@ -0,0 +1,78 @@
+---
+title: NGINX configuration
+weight: 277
+---
+## 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/).
+
+## Create NGINX Configuration
+
+After installing NGINX, you need to create the NGINX config file, `/etc/nginx/conf.d/rancher.conf`, with the IP addresses for your Linux nodes, chosen FQDN and location of the certificate file and certificate key file.
+
+1. Copy and paste the code sample below into your favorite text editor. Save it as `/etc/nginx/conf.d/rancher.conf`.
+
+    **Example NGINX config:**
+    ```
+    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;
+        }
+    }
+    
+    server {
+        listen 80;
+        server_name FQDN;
+        return 301 https://$server_name$request_uri;
+    }
+    ```
+
+2. In `/etc/nginx/conf.d/rancher.conf`, replace `IP_NODE_1`, `IP_NODE_2`, and `IP_NODE_3` with the IPs of your Linux hosts.
+3. In `/etc/nginx/conf.d/rancher.conf`, replace `FQDN` with the FQDN you chose for your Rancher installation.
+4. In `/etc/nginx/conf.d/rancher.conf`, replace `/certs/fullchain.pem` with the path to your certificate. If there are intermediates required for you certificate, they should be included in this file.
+5. In `/etc/nginx/conf.d/rancher.conf`, replace `/certs/privkey.pem` with the path to your certificate key.
+
+## Run NGINX
+
+* Reload or restart NGINX
+
+    ````
+    # Reload NGINX
+    nginx -s reload
+
+    # Restart NGINX
+    # Depending on your Linux distribution
+    service nginx restart
+    systemctl restart nginx
+    ````
+
+## Browse to Rancher UI
+
+You should now be to able to browse to `https://FQDN`.
@@ -0,0 +1,435 @@
+---
+title: High Availability Installation with External Load Balancer (TCP/Layer 4)
+weight: 275
+---
+This set of instructions creates a new Kubernetes cluster that's dedicated to running Rancher in a high-availability (HA) configuration. 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)
+
+![Rancher HA]({{< 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.
+
+1. [Provision Linux Hosts](#1-provision-linux-hosts)
+
+	Provision three Linux hosts to serve as your Kubernetes cluster.
+
+2. [Configure Load Balancer](#2-configure-load-balancer)
+
+	Configure your load balancer to have a highly available single point of entry to your Rancher cluster.
+
+3. [Configure DNS](#3-configure-dns)
+
+	Make your setup accessible using a DNS name by configuring the DNS to point to your loadbalancer.
+
+4. [Download RKE](#4-download-rke)
+
+	[RKE](https://github.com/rancher/rke/releases) is a fast, versatile Kubernetes installer that you can use to install Kubernetes on your Linux hosts.
+
+5. [Download RKE Config File Template](#5-download-config-file-template)
+
+	RKE uses a YAML config file to install and configure your Kubernetes cluster. Download one of our RKE config file templates to get started.
+
+6. [Configure Nodes](#6-configure-nodes)
+
+	Configure the **Nodes** section of the RKE config template.
+
+7. [Configure Certificates](#7-configure-certificates)
+
+	Configure the **Certificates** part of the template too.
+
+8. [Configure FQDN](#8-configure-fqdn)
+
+	And the **FQDN** part.
+
+9. [Back Up Your RKE Config File](#9-back-up-your-rke-config-file)
+
+	After you've completed configuration of the RKE config file: 1. it's no longer a template since you'll be using it, and 2. you should back up the RKE config file to a safe place. You will reuse this file for upgrades later.
+
+10. [Run RKE](#10-run-rke)
+
+	Run RKE to deploy Rancher to your cluster.
+
+11. [Back Up Auto-Generated Config File](#11-back-up-auto-generated-config-file)
+
+	During installation, RKE generates a config file that you'll use later for upgrades. Back it up to a safe location.
+
+<br/>
+
+## 1. Provision Linux Hosts
+
+Before you install Rancher, confirm you meet the host requirements. Provision 3 new Linux hosts using the requirements below.
+
+### Host Requirements
+
+#### Operating System
+
+{{< requirements_os >}}
+
+#### Hardware
+
+{{< requirements_hardware >}}
+
+#### Software
+
+{{< requirements_software >}}
+
+{{< note_server-tags >}}
+
+#### Ports
+
+The following diagram depicts the basic port requirements for Rancher. For a comprehensive list, see [Port Requirements]({{< baseurl >}}/rancher/v2.x/en/installation/references/).
+
+![Basic Port Requirements]({{< baseurl >}}/img/rancher/port-communications.png)
+
+## 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/ha-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/).
+
+### 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).
+
+    **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. Download RKE
+
+RKE is a fast, versatile Kubernetes installer that you can use to install Kubernetes on your Linux hosts. We will be using RKE to setup our cluster and run Rancher.
+
+1. From your workstation, open a web browser and navigate to our [RKE Releases](https://github.com/rancher/rke/releases/latest) page. Download the latest RKE installer applicable to your Operating System:
+
+    - **MacOS**: `rke_darwin-amd64`
+    - **Linux**: `rke_linux-amd64`
+    - **Windows**: `rke_windows-amd64.exe`
+
+2. Make the RKE binary that you just downloaded executable. Open Terminal, change directory to the location of the RKE binary, and then run one of the commands below.
+
+    >**Using Windows?**
+    >The file is already an executable. Skip to [Download Config File Template](#5-download-config-file-template).
+
+    ```
+    # MacOS
+    $ chmod +x rke_darwin-amd64
+    # Linux
+    $ chmod +x rke_linux-amd64
+    ```
+
+3.  Confirm that RKE is now executable by running the following command:
+
+    ```
+    # MacOS
+    $ ./rke_darwin-amd64 --version
+    # Linux
+    $ ./rke_linux-amd64 --version
+    ```
+
+    **Step Result:** You receive output similar to what follows:
+    ```
+    rke version v<N.N.N>
+    ```
+
+## 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`](https://raw.githubusercontent.com/rancher/rancher/e9d29b3f3b9673421961c68adf0516807d1317eb/rke-templates/3-node-certificate.yml)
+	- [Template for certificate signed by recognized CA<br/> `3-node-certificate-recognizedca.yml`](https://raw.githubusercontent.com/rancher/rancher/d8ca0805a3958552e84fdf5d743859097ae81e0b/rke-templates/3-node-certificate-recognizedca.yml)
+
+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.
+
+2. Update the `nodes` section with the information of your [Linux hosts](#provision-linux-hosts).
+
+    For each node in your cluster, update the following placeholders: `IP_ADDRESS_X` and `USER`.
+
+```
+nodes:
+  - address: IP_ADDRESS_1
+    # THE IP ADDRESS OR HOSTNAME OF THE NODE
+	user: USER
+    # USER WITH ADMIN ACCESS. USUALLY `root`
+	role: [controlplane,etcd,worker]
+	ssh_key_path: ~/.ssh/id_rsa
+    # PATH TO SSH KEY THAT AUTHENTICATES ON YOUR WORKSTATION
+    # USUALLY THE VALUE ABOVE
+  - 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
+```
+
+## 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:
+
+- [Option A—Bring Your Own Certificate: Self-Signed](#option-a-bring-your-own-certificate-self-signed)
+- [Option B—Bring Your Own Certificate: Signed by Recognized CA](#option-b-bring-your-own-certificate-signed-by-recognized-ca)
+
+### 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.
+
+    **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.
+
+
+    **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==
+    ```
+
+### Option B—Bring Your Own Certificate: Signed by Recognized CA
+
+>**Note:**
+> If you are using Self Signed Certificate, [click here](#option-a-self-signed-certificate) 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](#ssl-faq-troubleshooting) 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==
+```
+
+## 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. 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. 
+
+## 10. 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.
+
+```
+# MacOS
+./rke_darwin-amd64 up --config rancher-cluster.yml
+# Linux
+./rke_linux-amd64 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
+```
+
+## 11. 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 Availablility Back Up and Restoration]({{< baseurl >}}/rancher/v2.x/en/installation/backups-and-restoration/ha-backup-and-restoration).
+- Create a Kubernetes cluster: [Creating a Cluster]({{ <baseurl> }}/rancher/v2.x/en/tasks/clusters/creating-a-cluster/).
+
+<br/>
+
+## FAQ and Troubleshooting
+
+{{< ssl_faq_ha >}}
@@ -0,0 +1,172 @@
+---
+title: Amazon NLB configuration
+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**.
+
+
+## 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**.
+
+![EC2 Load Balancing section]({{< baseurl >}}/img/rancher/ha/nlb/ec2-loadbalancing.png)
+
+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/>
+![Target group 443]({{< baseurl >}}/img/rancher/ha/nlb/create-targetgroup-443.png)
+
+<hr>
+**Screenshot Target group TCP port 443 Advanced settings**<br/>
+![Target group 443 Advanced]({{< baseurl >}}/img/rancher/ha/nlb/create-targetgroup-443-advanced.png)
+
+<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/>
+![Target group 80]({{< baseurl >}}/img/rancher/ha/nlb/create-targetgroup-80.png)
+
+<hr>
+**Screenshot Target group TCP port 80 Advanced settings**<br/>
+![Target group 80 Advanced]({{< baseurl >}}/img/rancher/ha/nlb/create-targetgroup-80-advanced.png)
+
+<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**.
+
+![Edit target group 443]({{< baseurl >}}/img/rancher/ha/nlb/edit-targetgroup-443.png)
+
+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/>
+
+![Add targets to target group 443]({{< baseurl >}}/img/rancher/ha/nlb/add-targets-targetgroup-443.png)
+
+<hr>
+**Screenshot Added targets to target group TCP port 443**<br/>
+
+![Added targets to target group 443]({{< baseurl >}}/img/rancher/ha/nlb/added-targets-targetgroup-443.png)
+
+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.
@@ -0,0 +1,40 @@
+---
+title: 404 - default backend
+weight: 30
+---
+
+To debug issues around this error, you will need to download the command-line tool `kubectl`. See [Install and Set Up kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/) how to download `kubectl` for your platform.
+
+When you have made changes to `rancher-cluster.yml`, you will have to run `rke remove --config rancher-cluster.yml` to clean the nodes, so it cannot conflict with previous configuration errors.
+
+### Possible causes
+
+The nginx ingress controller is not able to serve the configured host in `rancher-cluster.yml`. This should be the FQDN you configured to access Rancher. You can check if it is properly configured by viewing the ingress that is created by running the following command:
+
+```
+kubectl --kubeconfig kube_config_rancher-cluster.yml get ingress -n cattle-system -o wide
+```
+
+Check if the `HOSTS` column is displaying the FQDN you configured in the template, and that the used nodes are listed in the `ADDRESS` column. If that is configured correctly, we can check the logging of the nginx ingress controller.
+
+The logging of the nginx ingress controller will show why it cannot serve the requested host. To view the logs, you can run the following command
+
+```
+kubectl --kubeconfig kube_config_rancher-cluster.yml logs -l app=ingress-nginx -n ingress-nginx
+```
+
+<b>Errors</b>
+
+* `x509: certificate is valid for fqdn, not your_configured_fqdn`
+
+The used certificates do not contain the correct hostname. Generate new certificates that contain the chosen FQDN to access Rancher and redeploy.
+
+* `Port 80 is already in use. Please check the flag --http-port`
+
+There is a process on the node occupying port 80, this port is needed for the nginx ingress controller to route requests to Rancher. You can find the process by running the command: `netstat -plant | grep \:80`.
+
+Stop/kill the process and redeploy.
+
+* `unexpected error creating pem file: no valid PEM formatted block found`
+
+The base64 encoded string configured in the template is not valid. Please check if you can decode the configured string using `base64 -D STRING`, this should return the same output as the content of the file you used to generate the string. If this is correct, please check if the base64 encoded string is placed directly after the key, without any newlines before, in between or after. (For example: `tls.crt: LS01..`)
@@ -0,0 +1,24 @@
+---
+title: Troubleshooting High Availability Installation
+weight: 370
+---
+This section contains common errors seen when setting up a High Availability Installation.
+
+Choose from the following options:
+
+- [Generic troubleshooting]({{< baseurl >}}/rancher/v2.x/en/installation/troubleshooting-ha/generic-troubleshooting)
+
+	In this section, you can find generic ways to debug your Kubernetes cluster.
+
+- [Failed to set up SSH tunneling for host]({{< baseurl >}}/rancher/v2.x/en/installation/troubleshooting-ha/ssh-tunneling)
+
+	In this section, you can find errors related to SSH tunneling when you run the `rke` command to setup your nodes.
+
+- [Failed to get job complete status]({{< baseurl >}}/rancher/v2.x/en/installation/troubleshooting-ha/job-complete-status)
+
+	In this section, you can find errors related to deploying addons.
+
+- [404 - default backend]({{< baseurl >}}/rancher/v2.x/en/installation/troubleshooting-ha/404-default-backend)
+
+	In this section, you can find errors related to the `404 - default backend` page that is shown when trying to access Rancher.
+
@@ -0,0 +1,145 @@
+---
+title: Generic troubleshooting
+weight: 5 
+---
+
+Below are steps that you can follow to determine what is wrong in your cluster.
+
+* Double check if all the required ports are opened in your (host) firewall
+
+Double check if all the [required ports]({{< baseurl >}}/rancher/v2.x/en/installation/references/) are opened in your (host) firewall.
+
+* All nodes should be present and in **Ready** state
+
+To check, run the command:
+
+```
+kubectl --kubeconfig kube_config_rancher-cluster.yml get nodes
+```
+
+If a node is not shown in this output or a node is not in **Ready** state, you can check the logging of the `kubelet` container. Login to the node and run `docker logs kubelet`.
+
+* All pods/jobs should be in **Running**/**Completed** state
+
+To check, run the command:
+
+```
+kubectl --kubeconfig kube_config_rancher-cluster.yml get pods --all-namespaces
+```
+
+If a pod is not in **Running** state, you can dig into the root cause by running:
+
+<h3>Describe pod</h3>
+
+```
+kubectl --kubeconfig kube_config_rancher-cluster.yml describe pod POD_NAME -n NAMESPACE
+```
+
+<h3>Pod container logs</h3>
+
+```
+kubectl --kubeconfig kube_config_rancher-cluster.yml logs POD_NAME -n NAMESPACE
+```
+
+If a job is not in **Completed** state, you can dig into the root cause by running:
+
+<h3>Describe job</h3>
+
+```
+kubectl --kubeconfig kube_config_rancher-cluster.yml describe job JOB_NAME -n NAMESPACE
+```
+
+<h3>Logs from the containers of pods of the job</h3>
+
+```
+kubectl --kubeconfig kube_config_rancher-cluster.yml logs -l job-name=JOB_NAME -n NAMESPACE
+```
+
+* List all Kubernetes cluster events
+
+Kubernetes cluster events are stored, and can be retrieved by running:
+
+```
+kubectl --kubeconfig kube_config_rancher-cluster.yml get events --all-namespaces
+```
+
+* Check Rancher container logging
+
+```
+kubectl --kubeconfig kube_config_rancher-cluster.yml logs -l app=cattle -n cattle-system
+```
+
+* Check NGINX ingress controller logging
+
+```
+kubectl --kubeconfig kube_config_rancher-cluster.yml logs -l app=ingress-nginx -n ingress-nginx
+```
+
+* Check if overlay network is functioning correctly
+
+The pod can be scheduled to any of the hosts you used for your cluster, but that means that the NGINX ingress controller needs to be able to route the request from `NODE_1` to `NODE_2`. This happens over the overlay network. If the overlay network is not functioning, you will experience intermittent TCP/HTTP connection failures due to the NGINX ingress controller not being able to route to the pod.
+
+To test the overlay network, you can launch the following `DaemonSet` definition. This will run an `alpine` container on every host, which we will use to run a `ping` test between containers on all hosts.
+
+1. Save the following file as `ds-alpine.yml`
+
+    ```
+    apiVersion: apps/v1
+    kind: DaemonSet
+    metadata:
+      name: alpine
+    spec:
+      selector:
+          matchLabels:
+            name: alpine
+      template:
+        metadata:
+          labels:
+            name: alpine
+        spec:
+          tolerations:
+          - effect: NoExecute
+            key: "node-role.kubernetes.io/etcd"
+            value: "true"
+          - effect: NoSchedule
+            key: "node-role.kubernetes.io/controlplane"
+            value: "true"
+          containers:
+          - image: alpine
+            imagePullPolicy: Always
+            name: alpine
+            command: ["sh", "-c", "tail -f /dev/null"]
+            terminationMessagePath: /dev/termination-log
+    ```
+
+2. Launch it using `kubectl --kubeconfig kube_config_rancher-cluster.yml create -f ds-alpine.yml`
+3. Wait until `kubectl --kubeconfig kube_config_rancher-cluster.yml rollout status ds/alpine -w` returns: `daemon set "alpine" successfully rolled out`.
+4. Run the following command to let each container on every host ping each other (it's a single line command).
+
+    ```
+    echo "=> Start"; kubectl --kubeconfig kube_config_rancher-cluster.yml get pods -l name=alpine -o jsonpath='{range .items[*]}{@.metadata.name}{" "}{@.spec.nodeName}{"\n"}{end}' | while read spod shost; do kubectl --kubeconfig kube_config_rancher-cluster.yml get pods -l name=alpine -o jsonpath='{range .items[*]}{@.status.podIP}{" "}{@.spec.nodeName}{"\n"}{end}' | while read tip thost; do kubectl --kubeconfig kube_config_rancher-cluster.yml --request-timeout='10s' exec $spod -- /bin/sh -c "ping -c2 $tip > /dev/null 2>&1"; RC=$?; if [ $RC -ne 0 ]; then echo $shost cannot reach $thost; fi; done; done; echo "=> End"
+    ```
+
+5. When this command has finished running, the output indicating everything is correct is:
+
+    ```
+    => Start
+    => End
+    ```
+
+If you see error in the output, that means that the [required ports]({{< baseurl >}}/rancher/v2.x/en/installation/references/) for overlay networking are not opened between the hosts indicated.
+
+Example error output of a situation where NODE1 had the UDP ports blocked.
+
+```
+=> Start
+command terminated with exit code 1
+NODE2 cannot reach NODE1
+command terminated with exit code 1
+NODE3 cannot reach NODE1
+command terminated with exit code 1
+NODE1 cannot reach NODE2
+command terminated with exit code 1
+NODE1 cannot reach NODE3
+=> End
+```
@@ -0,0 +1,54 @@
+---
+title: Failed to get job complete status
+weight: 20
+---
+
+To debug issues around this error, you will need to download the command-line tool `kubectl`. See [Install and Set Up kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/) how to download `kubectl` for your platform.
+
+When you have made changes to `rancher-cluster.yml`, you will have to run `rke remove --config rancher-cluster.yml` to clean the nodes, so it cannot conflict with previous configuration errors.
+
+### Failed to deploy addon execute job [rke-user-includes-addons]: Failed to get job complete status
+
+Something is wrong in the addons definitions, you can run the following command to get the root cause in the logging of the job:
+
+```
+kubectl --kubeconfig kube_config_rancher-cluster.yml logs -l job-name=rke-user-addon-deploy-job -n kube-system
+```
+
+#### error: error converting YAML to JSON: yaml: line 9:
+
+The structure of the addons definition in `rancher-cluster.yml` is wrong. In the different resources specified in the addons section, there is a error in the structure of the YAML. The pointer  `yaml line 9` references to the line number of the addon that is causing issues.
+
+<b>Things to check</b>
+<ul>
+<ul>
+<li>Is each of the base64 encoded certificate string placed directly after the key, for example: `tls.crt: LS01...`, there should be no newline/space before, in between or after.</li>
+<li>Is the YAML properly formatted, each indentation should be 2 spaces as shown in the template files.</li>
+<li>Verify the integrity of your certificate by running this command `cat MyCertificate | base64 -d` on Linux, `cat MyCertificate | base64 -D` on Mac OS . If any error exists, the command output will tell you.
+</ul>
+</ul>
+
+#### Error from server (BadRequest): error when creating "/etc/config/rke-user-addon.yaml": Secret in version "v1" cannot be handled as a Secret
+
+The base64 string of one of the certificate strings is wrong. The log message will try to show you what part of the string is not recognized as valid base64.
+
+<b>Things to check</b>
+<ul>
+<ul>
+<li>Check if the base64 string is valid by running one of the commands below:</li>
+
+```
+# MacOS
+echo BASE64_CRT | base64 -D
+# Linux
+echo BASE64_CRT | base64 -d
+# Windows
+certutil -decode FILENAME.base64 FILENAME.verify
+```
+
+</ul>
+</ul>
+
+#### The Ingress "cattle-ingress-http" is invalid: spec.rules[0].host: Invalid value: "IP": must be a DNS name, not an IP address
+
+The host value can only contain a host name, as it is needed by the ingress controller to match the hostname and pass to the correct backend.
@@ -0,0 +1,42 @@
+---
+title: Failed to set up SSH tunneling for host
+weight: 10
+---
+
+### 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 accesing 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`.
@@ -0,0 +1,4 @@
+---
+title: Advanced Install Options
+weight: 250
+---