k8s-multicluster-ingress

My takeaway/distillation from this article basically comes down to this: * GKE clusters currently can be only in 1 region (say, us-central1) * But you can create multiple clusters around the world, and deploy the same app on them * Google Cloud provides global anycast IPs for load balancers * Anycast IPs are routed to the closest PoP/datacenter available to the visitor of your application * Then, the traffic is routed to the closest GKE cluster (without leaving Google's private worldwide network) * This way, you serve to the user from the nearest cluster * If a region goes offline (disaster scenario) or is under high load, the load balancer will start sending traffic to other nearby clusters I deployed the sample demo app provided at with this at http://35.190.71.87/ (probably won't work in a month or so). Depending on where you're visiti

How is that related to security policies? Also you can't run a GKE cluster across multiple regions, only multiple zones. If you have multiple clusters in different regions, you can use a NodePort service on each and manually setup a GSLB with a backend pointing to all of the GKE clusters. There is a solution being worked on though, called multi-cluster ingress: https://github.com/GoogleCloudPlatform/k8s-multicluster-ingr...