AWS Load Balancer Operator On ROSA

AWS Load Balancer Controller is a controller to help manage Elastic Load Balancers for a Kubernetes cluster.

• It satisfies Kubernetes Ingress resources by provisioning Application Load Balancers .
• It satisfies Kubernetes Service resources by provisioning Network Load Balancers .

Compared with default AWS In Tree Provider, this controller is actively developed with advanced annotations for both ALB and NLB . Some advanced usecases are:

• Using native kubernetes ingress with ALB
• Integrate ALB with WAF
• Specify NLB source IP ranges
• Specify NLB internal IP address

AWS Load Balancer Operator is used to used to install, manage and configure an instance of aws-load-balancer-controller in a OpenShift cluster.

Prerequisites

• A multi AZ ROSA cluster deployed with STS
• AWS CLI
• OC CLI

Environment

1. Prepare the environment variables

AWS VPC / Subnets

Note: This section only applies to BYO VPC clusters, if you let ROSA create your VPCs you can skip to the following Installation section.

1. Set Variables describing your VPC and Subnets:

2. Tag VPC with the cluster name

3. Add tags to Public Subnets

4. Add tags to Private Subnets

Installation

1. Create Policy for the aws load balancer controller

   Note: Policy is from AWS Load Balancer Controller Policy plus subnet create tags permission (required by the operator)

2. Create trust policy for ALB Operator

3. Create Role for ALB Operator

4. Create secret for ALB Operator

5. Install Red Hat AWS Load Balancer Operator

6. Install Red Hat AWS Load Balancer Controller

   Note: If you get an error here wait a minute and try again, it likely means the Operator hasn’t completed installing yet.

7. Check the Operator and Controller pods are both running

   You should see the following, if not wait a moment and retry.

Validate the deployment with Echo Server application

1. Deploy Echo Server Ingress with ALB

2. Curl the ALB ingress endpoint to verify the echoserver pod is accessible

3. Deploy Echo Server NLB Load Balancer

4. Test the NLB endpoint

Clean Up

1. Delete the Operator and the AWS Roles

2. If you wish to delete the policy you can run