Hacker News Reader

I do believe the AWS Load Balancer Controller on Kubernetes allows for sharing a single "physical" load balancer.

You have to set a load-balancer-name annotation https://kubernetes-sigs.github.io/aws-load-balancer-controll... to tie everything together to one load balancer. There is a downside where you have to have a few other annotations be the same value across your ingresses, but once you work around that, you're good to go.

View on HN

I couldn't find it easily specified in docs. This is a common use-case and part of why I avoid EKS for HTTP workloads is that I have tiny services I want to just make available and I don't want to have another full ELB sitting there. It isn't a cost thing primarily. It's that now I have another significant resource. I want all of these things on a misc LB.

What you need is an Ingress. You can just have one ELB front all of your services if you wish.

https://kubernetes.io/docs/concepts/services-networking/ingr...

Reply on news.ycombinator.com