I just added a second node to my k8s cluster (previously I had only one to test everything out).
Now my LoadBalancers health states there is an issue and when checking the LoadBalancer it say that the second droplet is down. Checking inside k8s I can access that droplet via cli and everything else seems to be just fine.
What is the issue here? I also cannot seem to 1 click install OpenFaas. It always states that there went something wrong.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
I just realized that the ingress pod is running on the first droplet, not the second. Does the ingress service have to run on each node?
Hi Purnima, thank you very much for your help. Since the server IP shouldn’t matter to my clients it’s all good. I changed it to Cluster and everything is running smooth.
The LB is typically checking a specific nodePort service not just checking whether a node is healthy. To save on overhead from unnecessary network hops between nodes, only nodes hosting pods for the LoadBalancer service will report as healthy.
When the externalnetworkpolicy setting on kubernetes services is set to “Local”. This means a node without a pod running locally for that service will reject the LB healthcheck and show as down.
externaltrafficpolicy set to “cluster” would allow the nodes to forward that traffic to other nodes that are hosting pods for that service. In this case even a node not hosting a pod for that particular service would show as “UP” as it would then just forward it to a node that can, including that extra network hop.
To change this setting for particular service uses the following command:
kubectl patch svc myservice -p ’{“spec”:{“externalTrafficPolicy”:“Cluster”}}’
An important thing to note here is that if using the externaltrafficpolicy of “cluster” you will lose the original client IP address due to this extra network hop. So if your application is checking for or dependent on knowing the client IP, the “Local” setting is required.
You can find more information on externaltrafficpolicy here: https://kubernetes.io/docs/tutorials/services/source-ip/#source-ip-for-services-with-type-nodeport
I hope this helps!
Best Regards, Purnima Kumari
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.