Bug 1566932

Summary: [RFE] Use OpenStack Designate for internal name resolution
Product: OpenShift Container Platform Reporter: Tomas Sedovic <tsedovic>
Component: InstallerAssignee: Tomas Sedovic <tsedovic>
Status: CLOSED WONTFIX QA Contact: Jon Uriarte <juriarte>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 3.11.0CC: aos-bugs, jokerman, mmccomas, racedoro
Target Milestone: ---Keywords: Triaged
Target Release: 3.12.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-23 15:13:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Tomas Sedovic 2018-04-13 07:57:32 UTC 
The OCP deployer will request using Designate within the standard openshift-ansible configuration. This includes configuring the desired domain of the OCP cluster (but this has to happen in all OCP deployments). They will use openshift-ansible to deploy OCP.

This will succeed, but they will have to configure the API and wildcard public DNS entries to make the cluster accessible.
Comment 1 Ramon Acedo 2018-04-23 15:13:37 UTC 
After a technical discussion on internal DNS resolution in OpenShift between Neutron DNS or Designate we will focus on Neutron DNS and not Designate for this use case.