Question
Kubernetes LB health check documentation questions
- Posted on December 4, 2019
- DigitalOcean Managed Kubernetes
Asked by Scott Miller
I noticed that in the documentation https://www.digitalocean.com/docs/kubernetes/how-to/configure-load-balancers/ the following statement is made
By default, the load balancer performs health checks on the worker nodes over HTTP on port 80 at the webserver root.
However, when I look at the LB configuration UI for a K8s cluster, it is set to tcp://0.0.0.0:30666
Which should it be? What if the scheduler puts all of the pods that respond to http on only one node? It seems like this default rule would direct traffic to a node that couldn’t serve it?
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!
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.
Get our biweekly newsletter
Sign up for Infrastructure as a Newsletter.
Hollie's Hub for Good
Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.
Become a contributor
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Hi there,
What youre seeing there is a nodeport that is where the LB checks the health on the node. If you use kubectl to describe the pertinent service you will see that this 30666 nodeport translates to a different container port (probably 80).
kubectl describe svc <service_name> give output like this:
… Port: http 80/TCP TargetPort: http/TCP NodePort: http 30541/TCP …
In my example the LB reaches the node on port 30541 but that traffic actually hits the container on port 80. That is what is meant by that sentence.