Does Nebari on AWS utilize the AWS Load Balancer Controller?

[mwengren]

Greetings,

This is related to an existing discussion topic I created recently: https://github.com/orgs/nebari-dev/discussions/3117, and also pertains to the public/private subnet configuration under discussion in #3004. Posting this new topic as I've learned quite a bit since then about AWS load balancers.

I don't see any evidence that Nebari leverages the AWS Load Balancer Controller for AWS deployments (https://github.com/kubernetes-sigs/aws-load-balancer-controller, https://kubernetes-sigs.github.io/aws-load-balancer-controller/latest/).

Has this been discussed previously at all? Or did i miss something and it is actually being used in Nebari AWS deployments?

I'm trying to deploy Nebari to an existing public/private subnet set up in a pre-existing VPC and running into various challenges.

Short story is that I've been able to deploy it successfully, but running into limitations either with my VPC/networking set up or with AWS load balancers in general that prevent me from deploying Nebari's load balancer in my public subnet(s) and allowing it to communicate with Nebari EKS cluster in the private subnet(s). It appears the AWS Load Balancer Controller might help with this, in that it might allow deploying an AWS NLB, rather than a classic load balancer, for one.

The Nebari docs on Ingress/Load Balancers are fairly light for AWS, and, so far, for my testing, annotations in the AWS LBC docs aren't working as expected, which indicates it may not be deployed at all within Nebari.