Member-only story
Introduction
GKE recommends Container Native load balancing. This allows the GCP load balancer to route directly to the pod’s IP using a mechanism called Alias IP, NEG. However, if the pods are not set properly, downtime will occur when the pods are evicted from the node due to cluster maintenance or the like. In this article, I will explain how Container Native Load Balancer works and how to properly configure Pods.
Container Native load balancing mechanism
As described in Container Native Load Balancing, there is a Custom Controller called NEG Controller in the Master node of GKE, and when a Service with a specific Annotation is registered, it seems that a NEG resource is created in GCP and the Pod associated with the Service is attached to NEG. .. Also, as the name of the zonal network endpoint group suggests, a NEG is created for each zone, and the pod belongs to the NEG of the zone in which it exists.
