public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-27 05:28:22 +00:00
Code Issues Packages Projects Releases Wiki Activity

updating alb procedure

Browse Source
This commit is contained in:
Mark Bishop
2018-04-27 12:40:09 -07:00
committed by Denise
parent 305fed97d9
commit 44ba88388e
1 changed files with 45 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rancher/installation/load-balancing-config/configuring-amazon-alb.md
+45 -14
View File
@@ -20,7 +20,7 @@ Configuring an Amazon ALB is a multistage process. We've broken it down into mul
Use Amazon's Wizard to create an Application Load Balancer. As part of this process, you'll add one of the target groups you created in **1. Create Target Groups**.
4. [Add Your Second Target Group](#placeholder)
4. [Add Your Second Target Group](#add-your-second-target-group)
The Wizard in **3. Create Your ALB** only allows you to add a single target group. Go back into Amazon's console and add the second target group manually.
@@ -29,6 +29,8 @@ Configuring an Amazon ALB is a multistage process. We've broken it down into mul
Your first ALB configuration step is to create two target groups: one for HTTP, the other for HTTPS.
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)
@@ -42,15 +44,15 @@ Protocol | `HTTP`
Port | `80`
Target type | `instance`
VPC | Choose your VPC
Protocol<br/>(Health Check) | `HTTPS`
Protocol<br/>(Health Check) | `HTTP`
### Target Group 2 (HTTPS)
Option | Setting
----------------------------|------------------------------------
Target Group Name | `rancher-http-443`
Protocol | `HTTP`
Target Group Name | `rancher-https-443`
Protocol | `HTTPS`
Port | `443`
Target type | `instance`
VPC | Choose your VPC
@@ -64,16 +66,20 @@ Next, add your Kubernetes nodes assigned either the `controlplane` or `worker` r
### Create Your ALB
1. From your web browser, navigate to the [Amazon Elastic Load Balancing Console](https://aws.amazon.com/elasticloadbalancing/).
Use Amazon's Wizard to create an Application Load Balancer. As part of this process, you'll add one of the target groups you created in [Create Target Groups](#create-target-groups).
2. Click **Get Started with Elastic Load Balancing** and sign in.
1. From your web browser, navigate to the [Amazon EC2 Console](https://console.aws.amazon.com/ec2/).
3. Choose **Application Load Balancer**.
2. From the navigation pane, choose **LOAD BALANCING** > **Load Balancers**.
4. Complete the **Step 1: Configure Load Balancer** form.
3. Click **Create Load Balancer**.
4. Choose **Application Load Balancer**.
5. Complete the **Step 1: Configure Load Balancer** form.
- **Basic Configuration**
- Name: `rancher-ha-http-https`
- Name: `rancher-http-https`
- Scheme: `internet-facing`
- IP address type: `ipv4`
- **Listeners**
@@ -84,19 +90,44 @@ Next, add your Kubernetes nodes assigned either the `controlplane` or `worker` r
- **Availability Zones**
- Select Your **VPC** and **Availability Zone**.
- Select Your **VPC** and **Availability Zones**.
5. Complete the **Step 2: Configure Security Settings** form.
6. 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 3: Configure Security Groups** form.
7. Complete the **Step 4: Configure Routing** form. Add one of your [target groups](#create-target-groups) using the form.
8. Complete the **Step 4: Configure Routing** form.
>**User Action:** You must add _both_ target groups to your routing configuration, but Amazon's ALB Wizard limits you to add a single target group.
1. From the **Target Group** drop-down, choose **Existing target group**.
2. Add target group `rancher-http-80`.
>**Note:** The wizard lets you add only one group. You will add your second group in the next procedure, [Add Your Second Target Group](#add-your-second-target-group).
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**.
### Add Your Second Target Group
The load balancer is created, but you still need to add your second target group. Use the Amazon EC2 Console and add the second target group manually.
1. From the navigation pane, choose **LOAD BALANCING** > **Load Balancers**.
2. From the grid of load balancers, select your load balancer.
3. Select the **Listeners** tab. Select the `HTTPS: 43` **Listener ID**. Then click **Edit**.
4. From the **Default target group** drop-down, select `rancher-https-443`. Click **Save**.
5. Review the **Listeners** tab to make sure the protocols for the **Listener ID**s and **Rules** match. The following **Listener ID**s should be matched to the following **Rules**:
- `HTTP: 80`: `rancher-http-80`
- `HTTPS:443`: `rancher-https-443`