GKE deployment ignores regions value in weaver.toml for serviceweaver-config cluster deployment about weaver HOT 3 CLOSED

Currently, yes, the config cluster is always us-central1: https://github.com/ServiceWeaver/weaver-gke/blob/d3d4b98803fe204c58ecdd7e26c552926d247f1e/internal/gke/gke.go#L68-L69

I'll let @spetrovic77 elaborate on this :)

from weaver.

Thanks for filing the issue. What Michael said is correct.

A bit of background. GKE load-balancing libraries require configuration from a single cluster. This cluster needs to run somewhere, hence the need to pick a single region to run it in. We just happened to pick us-central1.

In addition to this configuration cluster, we additionally start application clusters in each region you specify in your TOML file, i.e., europe-west2 in your example.

Note that the configuration cluster is not on the request path for your application. It is used for configuring the load-balancers, for controling the rollouts of new application versions, and other centralized functionalities like that.

To help reduce the GKE costs for you in running this extra cluster, all of our GKE clusters run as bare-bones as possible.

from weaver.

Hi @mwhittaker @spetrovic77, thanks for the explanation.

I see that it doesn't affect the deployed application directly. However, I don't see any advantages of always picking the US region for the configuration cluster.

Even more, for example, talking about development environments, it's not always important to have multi-zonal or even multi-regional resources. It's much cheaper to keep everything in a single zone/region and expand it only in further environments (alpha, beta etc).
After all, having the possibility to configure all clusters regions/zones can bring benefits.

from weaver.