This is more of a research question that anything as I've tried to scour the internet. But I'm wondering the following setup and if is possible. I have:
region a-aws and region b-aws. Either region could have 1 to N eureka servers that sync between themselves, but not cross region (this is key).
App registering to region b-aws as a server, but wants to look up services as the discovery client in either a-aws or b-aws. Is this possible and how do I set up the discovery client to do so and not having the application switch it's current eureka registration server.
I'm trying to debug a new env we are setting up and noticing the server registration flip when we don't want it to as we have functionality for the eureka client to be able to lookup services in either region. The reason being for this env, we want the regions isolated and not able to cross-sync eureka registrations.
What i'm seeing in our logs:
2018-11-28T20:34:11.97+0000 [APP/PROC/WEB/0]OUT 2018-11-28T20:34:11.975Z WARN 0 [DiscoveryClient-3] com.netflix.discovery.DiscoveryClient: DISCOVERY: Could not pick a zone based on preferred zone settings. My zone - defaultZone, preferSameZone- true. Defaulting to a-aws
2018-11-28T20:34:11.97+0000 [APP/PROC/WEB/0]OUT 2018-11-28T20:34:11.975Z INFO 0 [DiscoveryClient-3] com.netflix.discovery.DiscoveryClient: Updating the serviceUrls as they seem to have changed from [https://b-aws/eureka/] to [https://a-aws/eureka/]
John