Diagram
Three GKE traffic paths side by side: ClusterIP for internal clients, NodePort via node IP and port, and LoadBalancer via cloud load balancer external IP, each forwarding from Service port to Pod targetPort.
Service Exposure and Network Connectivity
Exposing an application in GKE connects three parts. The frontend is the network location that listens for traffic, including its network, IP address, ports, and protocols. Routing and load balancing define how traffic is processed and sent to backends, and backends are the Pod endpoints that GKE updates dynamically. In GKE, the Service controller watches the declarative Service manifest and creates the needed load balancer, IP address, and firewall rules automatically.
Domain 10 of 11
24 practice questions
Practice this DomainLast updated