Nginx [SOLVED]: gke nginx lb health checks / can't get all instances in a "healthy" state

Nginx [SOLVED]: gke nginx lb health checks / can't get all instances in a "healthy" state

Home Forums Nginx Nginx [SOLVED]: gke nginx lb health checks / can't get all instances in a "healthy" state

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #36695

    Anonymous

    QuestionQuestion

    Using nginx nginx-ingress-controller:0.9.0, below is the permanent state of the google cloud load balancer :

    enter image description here

    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

    Here’s the service/deployment used

    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

    #36696

    Anonymous

    Accepted AnswerAnswer

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

    If you scale your Deployment to 2 replicas, 2 nodes will be healthy, etc.

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

    Source: https://stackoverflow.com/questions/47955064/gke-nginx-lb-health-checks-cant-get-all-instances-in-a-healthy-state
    Author: coreypobrien
    Creative Commons License
    This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.