Question

Load Balancer not forwarding to kubernetes service on nodePort.

Posted April 1, 2018 3.9k views
CoreOS Load Balancing Kubernetes

Hi there,

I run a kubernetes cluster on Digital Ocean.

I created a service, which is exposed via type nodePort. I can access the service in my browser if I enter http://PublicNodeIp:31433.

Now I want to use a DigitalOcean Load Balancer to forward traffic from port 80 to the service, but it doesn’t work. If I enter the load balancer IP in the browser I get: 503 Service Unavailable.

The load balancer is configured to forward http port 80 to Droplet http port 31433

I’m not sure, but can it be that the Load Balancer doesn’t forward to the Public Droplet Ip? If this is the problem, how can I expose a Kubernetes Service using the Private Droplet Ip?

Add a comment
feluxe
By:
feluxe
Add a comment

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

3 answers
tylerdo April 3, 2018

What you are describing should work normally via the public IP address, however, Load Balancers default to using the private network if private networking is enabled on the target Droplets. In this case, since you are using Kubernetes, I assume private networking is enabled.

I recommend that you expose the service on the private IP address instead and check back.

Reply Report
gabrpind February 8, 2019

I have the same error

Reply Report
demetrishoplaros May 28, 2019
How to Set Up an Nginx Ingress with Cert-Manager on DigitalOcean Kubernetes
by Hanif Jetha
In this tutorial, learn how to set up and secure an Nginx Ingress Controller with Cert-Manager on DigitalOcean Kubernetes.
Reply Report
Submit an Answer

Related

Looking for something else?

Ask a new question Search for more help