I’m trying to figure out why my service (type: LoadBalancer) isn’t working. This is running on AWS. I followed the steps in Debug Services - Kubernetes but can’t find any smoking gun. In particular, when ssh’ing into a cluster node, the following all work: nslookup <fq service name> <dns ip> cur…

What is the problem you see? Is a load balancer created on AWS (like browsing the AWS console)? Is there any event in the objects (svc)? If you have the load balancer on AWS created, see the listener it is using (in it’s config). Is it listening in which port? And to which port is forwards traffic …

Hi Rodrigo, thanks for your response. The one thing I noticed is that all of the instances for the broken service’s load balancer are listed as ‘out of service’ (and - not surprisingly - for the healthy service they are ‘in service’), so I need to dig into that.

Great. And which port is using for the health check? Is it using the nodePort of the service? If it is, then my next bet would be that the security group the load balancer is using can’t connect to the workers on that node. So, I’d make sure to accept incoming connections from the security group th…

Hi Rodrigo, your guess was correct, the health check was configured incorrectly (in this case, the nodeport it was using wasn’t serving anything). When I manually reconfigured the load balancer to use a different port, one that’s actually listened on, it worked. Thanks for your help! A follow-on q…

Glad it worked! Yes, registering all is intended. The thing is the following: The ELB does not know about pods, it knows about VMs instances. So, you can only register instances and not pods. Then, how do you distribute traffic evenly across pods? One option is to register all nodes as backends an…

Can you please tell how to let Kubernetes do the loadbalacning for pods as you mentioned above? Does it do it by-default if you expose a service like in the tutorial Hello Minikube - Kubernetes using kubectl expose deployment hello-node --type=LoadBalancer --port=8080 Would be helpfull if you can…

Yes, it is done when you expose the service like that. No need to do anything special :slight_smile:

Yes, it happens. Load balancing is done using iptables rules (if using iptables for kube-proxy, if using something else, then something else). Basically, when a request goes to a service IP, iptables routes it to one of the pods using a probability (so, if you have 2 pods, 50% of the times, more or…

@rata Thanks. I read the Services document which also describes the same. It says ‘By default, kube-proxy in iptables mode chooses a backend at random… If kube-proxy is running in iptables mode and the first Pod that’s selected does not respond, the connection fails. This is different from userspa…

Not sure about which problem you are talking about. It’s another thread? Will look later :slight_smile:

LoadBalancer service not working

General Discussions

mohibk August 6, 2019, 5:29pm 13

Sorry for mixing two things. Yes it is the another thread that i reffered here Loadbalancing across pods in a service using minikube .I shall put this comment there for reference.

Topic		Replies	Views
Kubernetes LoadBalancer service not exposed to Browser General Discussions	0	1550	December 12, 2021
Exposing kubernetes app using AWS Elastic LoadBalancer General Discussions	4	3415	February 1, 2019
Loadbalancer service in AWS EC2 instances without using AKS General Discussions	3	1291	September 21, 2024
AWS Network Load Balancer health check failed General Discussions	0	565	April 27, 2021
Service and endpoint General Discussions	3	1411	July 15, 2022

LoadBalancer service not working

Related topics