A service VIP is a routable virtual IP address that exposes a Service through a cluster load balancer. Traffic sent to the VIP reaches the load balancer, the Service NodePort on a node, and finally the selected Pod on its target port. section 10.3.2
Use the exposure pattern that matches the traffic:
- Expose a TCP-based Service with type LoadBalancer; the configuration creates a Service VIP that clients can access. section 10.4.1
- Expose web-based Services through Ingress, using an L3/L4 load balancer to publish an Ingress VIP and an L7 controller to enforce routing rules. section 10.3.2 section 10.4.1
- Use Service VIPs between clusters when network connectivity allows Services and Pods in one cluster to reach a Service in another. section 10.3.2
Cross-cluster request path
A Service in one Anthos GKE cluster receives a request from a workload in another cluster. The request targets the first Service's VIP, crosses the reachable network, enters the destination load balancer, passes through the Service NodePort, and reaches the desired Pod. section 10.3.2
Use the topology diagram to trace Service VIP traffic across Anthos GKE clusters, load balancers, nodes, and Pods. section 10.3.2
