Lab 7.1 Why curl on LoadBalancer:NodePort doesn't work ?

SebastienDionne

I have a question. Why I can't connect to my LoadBalancer IP with the nodeport ?

NAME         TYPE           CLUSTER-IP      EXTERNAL-IP      PORT(S)        AGE    SELECTOR
deploy       LoadBalancer   10.100.26.91    192.168.50.200   80:31335/TCP   3d     app=deploy
kubernetes   ClusterIP      10.96.0.1       <none>           443/TCP        30d    <none>
nginx        ClusterIP      10.109.9.141    <none>           443/TCP        26d    app=nginx
registry     ClusterIP      10.101.132.79   <none>           5000/TCP       26d    app=registry
secondapp    LoadBalancer   10.103.86.124   192.168.50.201   80:32000/TCP   112s   example=second

curl http://192.168.50.201:80 works but not curl http://192.168.50.201:32000 ?

chrispokorni

Hi @SebastienDionne,

The NodePort is designed to work with the Node/Host IP, as it is a Port of the Node. An external LB may be able to listen on the port with the same value as the nodeport, but that may require additional configuration of the LB.

Regards,
-Chris

SebastienDionne

thanks