Feature Overview (aka. Goal Summary)  

Use customer managed DNS solution instead of only specific openshift-install supported DNS services (such as AWS Route53, Google Cloud DNS, etc...) for OpenShift IPI deployments into main supported cloud providers.

• Phase 1 (Proposed for OCP 4.15) - Support external DNS for OpenShift on GCP
• Phase II (Proposed for OCP 4.16) - Support external DNS for OpenShift on AWS and Azure

Goals (aka. expected user outcomes)

Enable customers to deploy full stack automated OpenShift on main cloud providers using their own DNS service instead of the cloud provider (AWS Route 53, Google Cloud DNS, etc...)

Requirements (aka. Acceptance Criteria):

Installation support for performing an installer-provisioned infrastructure deployment to AWS, GCP and Azure using an external DNS service.

Use Cases (Optional):

As an administrator, I would like to deploy OpenShift 4 clusters to main cloud providers leveraging my custom DNS service.

Out of Scope

The Installer to manage (create/update/delete) the required DNS records to deploy OpenShift on these cloud providers or integrate with those DNS services in any way

Background

While cloud-based DNS services provide convenient hostname management, there's a number of regulatory and operational constraints customers face prohibiting the use of those DNS hosting services on public cloud providers.

This is the continuation of the work started in OCPBU-12

Documentation Considerations

How to leverage external DNS services while deploying OpenShift on AWS, Azure and GCP will be documented extending the existing documentation for OpenShift deployments on these providers.