My takeaway/distillation from this article basically comes down to this:<p>* GKE clusters currently can be only in 1 region (say, us-central1)<p>* But you can create multiple clusters around the world, and deploy the same app on them<p>* Google Cloud provides global anycast IPs for load balancers<p>* Anycast IPs are routed to the closest PoP/datacenter available to the visitor of your application<p>* Then, the traffic is routed to the closest GKE cluster (without leaving Google's private worldwide network)<p>* This way, you serve to the user from the nearest cluster<p>* If a region goes offline (disaster scenario) or is under high load, the load balancer will start sending traffic to other nearby clusters<p>I deployed the sample demo app provided at with this at <a href="http://35.190.71.87/" rel="nofollow">http://35.190.71.87/</a> (probably won't work in a month or so). Depending on where you're visiting, you'll be routed to the closest datacenter the app is deployed in.<p>The demo app source code is here: <a href="https://github.com/GoogleCloudPlatform/k8s-multicluster-ingress/tree/master/examples/zone-printer" rel="nofollow">https://github.com/GoogleCloudPlatform/k8s-multicluster-ingr...</a> You can try it out yourself if you have a GCP account.<p>Disclaimer: I work on GKE at Google.
I think this is the first of these stories that I have realized has no relevance to me <i>BEFORE</i> I click on the link rather than after. (Currently working on Kubernetes stuff, but all the GKE posts here have not been that useful, though I have played with GKE and like it)