Summary

GEO conflict between 2 DNSPolicies happens when both policies have defaultGeo property set to True and both have different geo locations (US and EU for example). Which results in undetermined state where it is not clear what DNSPolicy has the default geo location information for dns provider to use.

Test cases

We need to have the test which will verify that both policies will reach some consistent state and indicate that geo conflict is happening.

Additional context

As of date of this issue creation there is a bug where DNSPolicies can't handle the geo conflict correctly and rapidly changing their states from successful to failed and back. Also resulting in dns provider records switching their default geo record every few seconds.
Kuadrant/dns-operator#265 Kuadrant/dns-operator#210