Timofey Ilinykh

@ytsarev to my understanding, with one k8gb instance, deployed to environment A and configured to use that environment-specific EdgeDNS (e.g. AWS and Route53), and then another k8gb instance deployed on...

Or did you mean some complex scenario, when for example we have workloads exposed with different zones in the cluster that need to be resolved using different EdgeDNS providers?

Adding a few supporting facts as food for thought: - AWS: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/hosted-zone-private-considerations.html#hosted-zone-private-considerations-delegating-subdomain: > You cannot create NS records in a private hosted zone to delegate responsibility for a subdomain. -...

@jkremser not sure we can raise that as a requirement, but rather as a recommendation, it is up to users to decide about their infra. There might be security reasons...

@jkremser I'd prefer to wait for the official v2 release. It still makes sense to build with git sha and check if k8gb is still able to work with older...

@kuritka what's the status of this one, can we close it?

@jkremser did #916 fix this issue, can we close it?

Currently, we're at level 2 (Seamless Upgrades), and I'm not sure we want to move up the ladder in the nearest future unless we have a request from the community....

@kuritka I'd suggest using `EDGE_DNS_PROTOCOL`, port is something that can be changed and it's not necessarily tied to a certain protocol type.

@ErikLundJensen I've enabled the issue creation in the AbsaOSS/coredns-helm Not sure if all changes made there have been pushed to the upstream. @k0da we might want to move this fork...