<p>I have installed my kubernetes cluster on Jelastic. Now, I tried to define a service of <code>LoadBalancer</code> type and would like it to be provided with an external IP. The external IP is currently marked as <code>pending</code>. What should I do to make it non-pending? Do I have to provide the worker nodes with an external IPv4?</p>
<p>In my current setup, my worker nodes have no IPv4 because I put an nginx load-balancer in front of the cluster:</p>
<p><a href="https://i.stack.imgur.com/hQnQ8.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/hQnQ8.png" alt="enter image description here" /></a></p>
<p>The IPv4 is set on the nginx node. Is that a problem? If I want to access my loadbalancer service inside of my kubernetes cluster, what should I do?</p>

Laurent Michel
<p>In Jelastic Public IP addresses have to be attached to worker nodes.
Every worker node has ingress controller instance running (based oт nginx/haproxy/traefik) with http/https listeners that can forward traffic to the  required service.</p>
<p>You have just to bind your domain as <a href="https://docs.jelastic.com/custom-domains/" rel="nofollow noreferrer">CNAME to Environment FQDN</a> and every your worker node can accept requests in RR-DNS mode.
Does this scenario works for you or you have a specific requirement to use external load balancer?</p>
<p>By default, when Public IPs are not attached to worker instances the traffic is going through the <a href="https://docs.jelastic.com/custom-domains/" rel="nofollow noreferrer">Shared Load Balancer</a>.</p>
<p>P.S. If you install Certification Manager Addon to your K8s cluster - you can also issue free Let's Encrypt certificates.</p>
