<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>For <code>LoadBalancer</code> service type to work, the cloud provider must implemenet the relevant APIs to get it to work.</p>
<p>With regard to <code>Jelastic</code>, as per their docs, they don't support it <a href="https://docs.jelastic.com/kubernetes-exposing-services/" rel="nofollow noreferrer">https://docs.jelastic.com/kubernetes-exposing-services/</a>:</p>
<blockquote>
<p>Jelastic PaaS does not support the LocaBalancer service type currently.</p>
</blockquote>
