Bug 1566932 - [RFE] Use OpenStack Designate for internal name resolution
Summary: [RFE] Use OpenStack Designate for internal name resolution
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
: 3.12.0
Assignee: Tomas Sedovic
QA Contact: Jon Uriarte
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-04-13 07:57 UTC by Tomas Sedovic
Modified: 2018-04-23 15:13 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-23 15:13:37 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.