Replicas/Load Balancer Mapping

December 6, 2018 731 views
Load Balancing Kubernetes

Please forgive me in advance for the nooby question. I created a deployment with 3 replicates running in 3 pods. My cluster consists of 5 nodes. I have a load balancer that takes the public IP and distributes the load across all 5 nodes in my cluster. Everything seems to be working fine, and all 5 nodes are healthy where it looks like it’s mapping to a port that is exposed via the pod.

I would have expected two of the mappings on the load balancer to be “unhealthy” and it only maps to the 3 active nodes with an active deployment. Can someone give me an education?

1 comment
  • My issue is kinda similar: I only have 1 node (to test) and 3 replicas/pods running for 1 deployment. This deployment is exposed via a LoadBalancer service (managed by DigitalOcean).

    LB shows this one node as healthy and it works great. However, when I deploy using the rolling update, the website temporarily goes down and node shows as unhealthy - despite the fact that at any given point in time at least 2 pods are running and accepting connections.

Be the first one to answer this question.