diff --git a/content/rancher/installation/load-balancing-config.md b/content/rancher/installation/load-balancing-config.md index 49cd2e00e36..59079365238 100644 --- a/content/rancher/installation/load-balancing-config.md +++ b/content/rancher/installation/load-balancing-config.md @@ -4,10 +4,123 @@ layout: single-docs weight: 300 --- -# Load Balancing Configuration +# External Load Balancer Configuration -## Option 1: Amazon ELB +Following {{< product >}} installation, you have the option of configuring an external load balancer to direct cluster traffic. + +## Option 1: Amazon ELB (Recommended) + +Amazon Elastic Load Balancer (ELB) is the load balancer most tested by {{< product >}}. You can set one up at Amazon Web Services (AWS). You have the option of using either an Application Load Balancer (ALB) or a Network Load Balancer (NLB). + +## Create Target Groups + +Regardless of your choice, ALB or ELB, your first load balancer configuration step is to create two target groups: one for HTTP, the other for HTTPS. + +[Amazon Documentation: Create a Target Group](https://docs.aws.amazon.com/elasticloadbalancing/latest/application/create-target-group.html) + +As you complete the procedure above, use the settings listed in the table below. + +### Target Group 1 (HTTP) + +Option | Setting +----------------------------|------------------------------------ +Target Group Name | `rancher-ha-http-80` +Protocol | For ALB: `HTTP`
For NLB: `TCP` +Port | `80` +Target type | `instance` +VPC | Choose your VPC +Protocol
(Health Check) | For ALB: `HTTPS`
For NLB: `TCP` + + +### Target Group 2 (HTTPS) + +Option | Setting +----------------------------|------------------------------------ +Target Group Name | `rancher-ha-http-443` +Protocol | For ALB: `HTTP`
For NLB: `TCP` +Port | `443` +Target type | `instance` +VPC | Choose your VPC +Protocol
(Health Check) | For ALB: `HTTPS`
For NLB: `TCP` + + +## Register Targets + +Next, add your Kubernetes nodes assigned either the `controlplane` or `worker` role to _both_ of your target groups. + +[Amazon Documentation: Register Targets with Your Target Group](https://docs.aws.amazon.com/elasticloadbalancing/latest/application/target-group-register-targets.html) + + + +### Completing ALB Configuration + +1. From your web browser, navigate to the [Amazon Elastic Load Balancing Console](https://aws.amazon.com/elasticloadbalancing/). + +2. Click **Get Started with Elastic Load Balancing** and sign in. + +3. Choose **Application Load Balancer**. + +4. Complete the **Step 1: Configure Load Balancer** form. + - **Basic Configuration** + + - Name: `rancher-ha-http-https` + - 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 Zone**. + +5. Complete the **Step 2: Configure Security Settings** form. + + >**Installing in a High-Availability Configuration?** + > - If you are using self-signed certificates, the certificate and key must be signed by the same certificate authority that signed `cattle-keys-server`. + > - If you are using SSL passthrough, you must use a certificate signed by a public certificate authority. + +6. Complete the **Step 3: Configure Security Groups** form. + +7. Complete the **Step 4: Configure Routing** form. Configure two **Target Groups** using the settings below. + + - Target Group 1: HTTP + + - **Target Group** + + - Name: `rancher-ha-http-80` + - Protocol: `HTTP` + - Port: `80` + - Target type: `instance` + - Protocol: + + - **Health Checks** + + - Protocol: `HTTPS` + + - Target Group 2: HTTPS + + - **Target Group** + + - Name: `rancher-ha-http-443` + - Protocol: `HTTPS` + - Port: `443` + - Target type: `instance` + + - **Health Checks** + + - Protocol: `HTTPS` + +### To Use Network Load Balancer: + +1. Open a web browser, navigate to the [Amazon Elastic Load Balancing Console](https://aws.amazon.com/elasticloadbalancing/), and then log in. + +## Option 3: NGINX + +NGINX is a popular application platform that can be used as a load balancer. ## Option 2: HAProxy -## Option 3: NGINX +Hey, guess what. You can use HAProxy too. diff --git a/content/rancher/installation/requirements/_index.md b/content/rancher/installation/requirements/_index.md deleted file mode 100644 index 9c1fd383332..00000000000 --- a/content/rancher/installation/requirements/_index.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: Requirements -draft: true -layout: single-docs -weight: 125 ---- - -# Requirements diff --git a/content/rancher/installation/requirements/node-requirements.md b/content/rancher/installation/requirements/node-requirements.md deleted file mode 100644 index 06525ba1f2e..00000000000 --- a/content/rancher/installation/requirements/node-requirements.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Node Requirements -draft: true -layout: single-docs -weight: 200 ---- -# Node Requirements - -When creating or importing a Kubernetes cluster, make sure that each node meets to following requirements. - -{{< requirements_os >}} - -{{< requirements_hardware >}} - -{{< requirements_software >}} - -## Port Requirements - -Open the following ports on your cluster nodes so that they can communicate with each other. - -{{< requirements_ports >}} diff --git a/content/rancher/installation/requirements/server-requirements-deployment-install.md b/content/rancher/installation/requirements/server-requirements-deployment-install.md deleted file mode 100644 index aeb8309fd7f..00000000000 --- a/content/rancher/installation/requirements/server-requirements-deployment-install.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: "Rancher Server Requirements: Existing Cluster Installs" -draft: true -layout: single-docs -weight: 175 ---- - -# Rancher Server Requirements: Existing Cluster Installs - -If you want to install {{< product >}} on a server in an existing Kubernetes cluster, you have some additional requirements that you need to account for. - -{{< requirements_os >}} - -{{< requirements_hardware >}} - -{{< requirements_software >}} - -## Port Requirements - -Open the following ports on your cluster nodes so that they can communicate with each other. - -{{< requirements_ports >}} diff --git a/content/rancher/installation/requirements/server-requirements.md b/content/rancher/installation/requirements/server-requirements.md deleted file mode 100644 index ea04d9d667e..00000000000 --- a/content/rancher/installation/requirements/server-requirements.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Rancher Server Requirements -draft: true -layout: single-docs -weight: 150 ---- - -# Rancher Server Requirements - -Before you install {{< product >}}, wrangle up these requirements. Use these requirements for most {{< product >}} Server installation scenarios. Yip! Yip! Yah! - ->**Want to install {{< product >}} in an existing Kubernetes cluster?** -> -> Refer to [these requirements](server-requirements-deployment-install.md) instead. - -{{< requirements_os >}} - -{{< requirements_hardware >}}