What

With RHCL each installation is unaware of any other installation by default. However this has some drawbacks when it comes to managing DNS for multiple clusters. 

• Each Cluster has to have a credential to access the DNS Provider
• RateLimits can be reached when reconciling the DNSRecords into the providers such as AWS Route 53
• Supporting on premise DNS providers such as Core DNS is not possible with this setup

RHCL should be able to support managing DNS without the need to integrate with a cloud DNS provider as this is how many enterprises require their DNS to be  Managed. As currently the cloud provider, is a shared syncronization mechnism we need a new way to discover and form a full DNS record set for multi-cluster ingress in scenerios where a cloud provider is not an option.

Requirements

• Must not require integration with an external cloud provider
• Must not require an additional instance of Core DNS for RHCL on every single cluster
• It must offer the same DNS features as we offer via DNSPolicy for the other DNS Providers (GEO and Weighted LoadBalancing, Status reporting based on Health Checks)

Out of Scope

• Removal and publishing of records based on DNS Health Checks this will be covered under a specific feature