Details
-
Feature Request
-
Resolution: Done
-
Blocker
-
None
-
False
-
False
-
0
-
0%
-
undefined
Description
1. Proposed title of this feature request
Support the AWS Load Balancer Controller for Ingress objects.
2. What is the nature and description of the request?
The AWS Load Balancer Controller provides a number of significant improvements when working natively with AWS components. This includes, primarily, the ALB support on Ingress objects.
The AWS Load Balancer Controller should be a supported/supportable operator available for day-2 installation on the cluster. The operator should be able to handle the necessary cloud authentication mechanisms (both Mint and Manual modes) in order to configure AWS resources appropriately (https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.2/deploy/installation/#iam-permissions).
Initially provide support for workload traffic, and add non-workload support (oauth, API, console) in a follow-on enhancement.
Ideally, we would support specification of ALB as simply as something like:
service.beta.kubernetes.io/aws-load-balancer-type: "alb"
3. Why does the customer need this? (List the business requirements here)
ALBs provide a significant number of improvements over CLBs and NLBs (https://docs.aws.amazon.com/elasticloadbalancing/latest/application/introduction.html#application-load-balancer-benefits), and many customers integrating natively with AWS are trying to use these benefits.
4. List any affected packages or components.
5. AWS will be retiring the EC2-Classic network on August 15, 2022. For more information: https://aws.amazon.com/vpc/faqs/