0

We are using GCP load balancer non-Classic HTTPS. We have two instance groups, one in Central and one in East. Right now it is sending all incoming traffic to only the nearest instance group. We actually want to turn off geo loadbalancing and just round-robbin the traffic across ALL instance groups.

How do we actually do that? This is not obvious from UI and documentation

A X
  • 469
  • 4
  • 10
  • 31
  • Is there a reason you want to do this? While the Global LB prefers to route to the closest region to the client, it will also route to the next (nearest) region if there is no capacity in the nearest region. Have a look at https://cloud.google.com/load-balancing/docs/backend-service#target-capacity – Gari Singh Feb 11 '23 at 08:46
  • @GariSingh Yeah this is basic. Azure Front Door, for example, can do this. This is yet another example of a non-obvious limitation in GCP that matters – A X Feb 12 '23 at 02:43
  • Could you point me to how you'd do this with Azure Front Door? I don't see how you'd do this there either. – Gari Singh Feb 12 '23 at 09:47

1 Answers1

1

There is a workaround available for this issue. You need to recreate a new load balancer for your instance group and need to reconfigure it with your desired functionalities (round robin algorithm in your case). However if you are trying to edit your existing load balancer’s config as of now there is no way, there is a similar issue and a feature request has been raised with google team for it for more updates.

Kranthiveer Dontineni
  • 167
  • 8
  • Thanks - I am happy to create a new one. Which screen do I select "Round Robin" in? I tried searching around and didn't see it in the create flow but maybe I just missed it – A X Jan 17 '23 at 04:41
  • In GCP each type of load balancer by default supports a particular algorithm for more information go through [load balancing methods](https://cloud.google.com/load-balancing/docs/features#load_balancing_methods) documentation. – Kranthiveer Dontineni Jan 17 '23 at 05:21
  • Thanks - OK I am looking at the screen for a new HTTPS Load Balancer Backend Configuration. There is a setting in Advanced called "Locality load balancing policy*". The default choice is Round Robin. However, there is no choice to NOT do locality load balancing at all and just do a pure Round Robin. Am I missing something? They all seem to be Locality Aware? I think this just sets what to use within a locality, but I want to configure how it decides which locality. – A X Jan 17 '23 at 06:04
  • If you are okay with using multiple load balancers, you can create an external load balancer and redirect the traffic to a regional LB for performing your round robin operations. – Kranthiveer Dontineni Jan 17 '23 at 08:44
  • Thanks - wouldn't that still geo-route to the closest region though? – A X Jan 17 '23 at 21:57
  • No you can use path based routing like for "EU" specify one path and for "US" specify one path eg: eu.example.com and us.example.com. – Kranthiveer Dontineni Jan 18 '23 at 04:52
  • But I don't want to do that. I just want it to round robin across all regions. Btw Azure front door can do this - it's pretty standard. – A X Jan 18 '23 at 04:53