Multi-cluster, Blue-green Traffic Splitting with the Gateway API
summary
Live demo shows Google Cloud’s GKE implementation of the Gateway API programming a Google global load balancer to route across three clusters using the Kubernetes-native resources: service export/import, Gateway, and HTTPRoute. Examples include header-based canary routing that targets gke3, traffic mirroring for capacity testing, and a concrete 70%/30% split where actual requests distribute roughly as expected, proving multi-cluster blue‑green and canary workflows work end to end.
AI-written summary · about
chapters (4)
related talks
14mEnabling Multi-Cluster Load Balancing with Gateway API and Envoy Gateway
29mGateway API: The new Kubernetes Ingress that Unifies Load Balancing and Network Configs
28mBeyond Kubernetes Ingress (with Gateway API)
22mCloud Native Multi Cluster/Multicloud Global Load Balancer for Kubernetes
10mLightning Talk: Make Way for the Gateway
33mExiting Ingress With the Gateway API
34mMulticluster Ingress Powered by Kubernetes Cluster Registry - Greg Harmon & Nikhil Jindal
36mGateway API The new way to travel north south
