Add geo load-balancing tests

[averevki]

Changes

• Change the list of additional clusters to only 2 (not required in the near feature)
• Reformat multicluster contest to support only 2 clusters

Tests

• Add geo load balancing test
• Add unsupported geocode test

Closes #496, closes #515

[trepel]

@averevki Could you please resolve the conflicts? It would make reviewing easier and you need to that anyway

[trepel]

I don't understand the reasoning behind doing this refactoring to Change the list of additional clusters to only 2. Why was it required?

[trepel]

I am seeing The DNS operation timed out. error while running resolver.resolve(hostname.hostname). Did you come across that?

[averevki]

I don't understand the reasoning behind doing this refactoring to Change the list of additional clusters to only 2. Why was it required?

We don't need this functionality for now. Right now, it's committing the same object on each cluster, and I need more flexibility in CR configuration on each cluster

[averevki]

I am seeing The DNS operation timed out. error while running resolver.resolve(hostname.hostname). Did you come across that?

You may be using wrong DNS servers. Or you are running under the internal network, which blocks non-internal dns

[trepel]

I tried each test modified in this PR, all good. I tried to modify the geo label to ES and I tried to remove it completely, the geo loadbalancing test failed as expected then. Code looks good to me, my understanding of it is that instead of crafting a request from certain GEO (DE or AU) or looking at DNS records in AWS the test specifically asks DE and AU DNS nameserver to resolve the same hostname and validates that external IP of right Gateway is returned. Nice!

[trepel]

Only thing that confuses me a little is that if I tried to resolve the hostname in https://dnschecker.org/ it took a few minutes till at least one AU server started resolving to "AU" Gateway external IP.