Container-native load balancing sends traffic from a GKE HTTP load balancer directly to Pod IPs through network endpoint groups (NEGs). Without NEGs, Ingress traffic reaches a node’s NodePort first; the GKE Dataplane then forwards it to a Pod, potentially on another node. Direct routing removes those extra hops and simplifies the traffic path. section 10.2.1
Pod readiness gates also let the load balancer assess health from outside the cluster, rather than relying only on in-cluster probes. Awareness of Pod startup, Pod loss, and VM loss helps keep traffic stable. section 10.2.1
For Services, container-native load balancing is enabled by default when all of these conditions hold:
- The Service was created in a GKE 1.17.6-gke.7 or later cluster. section 10.2.1
- The cluster is VPC-native, does not use Shared VPC, and does not use GKE network policy. section 10.2.1
Service annotation
A Service manifest can specify `cloud.google.com/neg: '{"ingress": true}'` to request a NEG for Ingress traffic. section 10.2.1
