I’m pretty much sure that is not supported, but maybe.
Suppose I have following setup:
Kong1 - rack1
Kong2 - rack2
Kong3 - rack3
we have Service and Upstream configured, with 3 targets:
T1 - rack1
T2 - rack2
T3 - rack3
obvious desire that requests that land to Kong1 will try T1 first, this can be done with weight configuration, but configuration is shared, so it will be the same for all Kong instances.
Workaround of this, we can encode rack in upstream name and use plugin to supply the correct servers, but I’m looking if something like that is available or planed to be available in Kong.
*rack in this case could be availability group, subnet, etc ( close server(s) )