Island mode isolates a cluster’s Pod and Service addressing from external routing while preserving direct communication among workloads inside the cluster. This permits multiple clusters to reuse the same IP schema without address overlap or exhaustion. section 10.2.2 section 10.3.2
Account for these deployment implications:
- Expose services externally through a load balancer, NodePort, and routable Service VIP; traffic is forwarded from the node to the target Pod. section 10.3.2
- Connect services across clusters through their routable VIPs, even when the underlying Pod and Service addresses remain cluster-local. section 10.3.2
- Use Ingress controllers when one externally reachable Ingress VIP must route to multiple services according to Ingress rules. section 10.3.2
- Use Anthos Service Mesh for service discovery across clusters; hybrid and multicloud designs also require connectivity between infrastructure environments. section 10.3.2
Hybrid multicluster access
A service in one Anthos GKE cluster accesses a service in another cluster through the destination Service VIP. The load balancer routes that traffic to a NodePort, which forwards it to the destination Pod. section 10.3.2
Use the hybrid multicluster networking diagram to trace how routable VIPs connect services while cluster-internal addresses remain isolated. section 10.3.2
