<p>Using nginx <code>nginx-ingress-controller:0.9.0</code>, below is the permanent state of the google cloud load balancer :</p>

<p><a href="https://i.stack.imgur.com/zT3mj.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/zT3mj.png" alt="enter image description here"></a></p>

<p>Basically, the single healthy node is the one running the nginx-ingress-controller pods. Besides not looking good on this screen, everything works super fine. Thing is, Im' wondering why such bad notice appears on the lb</p>

<p>Here's <a href="https://gist.github.com/benbonnet/14f0c3efc7a2edd7b50351e825e39353" rel="nofollow noreferrer">the service/deployment</a> used</p>

<p>Am just getting a little lost over how thing works; hope to get some experienced feedback on how to do thing right (I mean, getting green lights on all nodes), or to double check if that's a drawback of not using the 'official' gcloud l7 thing </p>

<p>Your <code>Service</code> is using the <code>service.beta.kubernetes.io/external-traffic: OnlyLocal</code> annotation. This configures it so that traffic arriving at the NodePort for that service will never go a <code>Pod</code> on another node. Since your <code>Deployment</code> only has 1 replica, the only node that will receive traffic is the one where the 1 Pod is running.</p>

<p>If you scale your <code>Deployment</code> to 2 replicas, 2 nodes will be healthy, etc.</p>

<p>Using that annotation is a recommend configuration so that you are not introducing additional network hops.</p>
