Add support for managing AWS Load Balancer Controller with EKS add-ons.
The Load Balancer Controller seems like something that should be on the controlplane rather than an add-on. Same goes for the CSI driver.
Here is an example of an issue we have where we find ourselves falling short between AWS & EKS with load balancers.
I would like to take advantage of VPC endpoint service to allow another AWS account to use private endpoint to talk to something running within kubernetes and not over public network.
Would look something like this:
AWS Account A [Lambda -> Private endpoint] -> Account B [ VPC endpoint service -> Internal NLB -> Kubernetes -> Service]
The problem here is kind of a chicken & egg situation that requires cluster post installs. We're not able to set up the VPC endpoint service until the NLB exists but the NLB won't exist until kubectl apply (helm install in our case) happens on the application side because that has the load balancer resource.
Our "hack around this:
Most helpful comment
Here is an example of an issue we have where we find ourselves falling short between AWS & EKS with load balancers.
I would like to take advantage of VPC endpoint service to allow another AWS account to use private endpoint to talk to something running within kubernetes and not over public network.
Would look something like this:
AWS Account A [Lambda -> Private endpoint] -> Account B [ VPC endpoint service -> Internal NLB -> Kubernetes -> Service]
The problem here is kind of a chicken & egg situation that requires cluster post installs. We're not able to set up the VPC endpoint service until the NLB exists but the NLB won't exist until kubectl apply (helm install in our case) happens on the application side because that has the load balancer resource.
Our "hack around this: