Bug 1393486

Summary:	[RFE] Dynamic DNS
Product:	OpenShift Container Platform	Reporter:	Eric Rich <erich>
Component:	RFE	Assignee:	Ben Bennett <bbennett>
Status:	CLOSED DEFERRED	QA Contact:	Xiaoli Tian <xtian>
Severity:	low	Docs Contact:
Priority:	medium
Version:	3.3.0	CC:	akostadi, aos-bugs, bbennett, bmcelvee, ccoleman, erich, jokerman, jpazdziora, mcurry, mmccomas, sukulkar, zzhao
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1347822	Environment:
Last Closed:	2019-04-18 21:16:20 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:
Bug Depends On:	1347822
Bug Blocks:

Description Eric Rich 2016-11-09 16:27:33 UTC

+++ This bug was initially created as a clone of Bug #1347822 +++

Description of problem:
As a user I want my routes to work as as soon as they are created. 
As an admin of OpenShift I want OpenShift to dynamicly create DNS entries so that I do not have to have a "wildcard" DNS entry for my router[s]. 

By default with some OpenShift configurations a "wildcard" dns name is used, and "default" routes are defined when I expose a service, however this relies on a "wildcard DNS entry" that some corporate policies may not allow. 

For this reason, OpenShift needs to be able to dynamically configure a DNS service of my choosing (like with v2) and create DNS entries (CNAMES) that point to the router[s] in the OpenShift cluster.

Comment 2 Eric Rich 2017-01-16 20:21:52 UTC

Note: We probably want to consider wiring Dynamic DNS to automatic certificate creation: https://docs.openshift.com/container-platform/3.3/dev_guide/secrets.html#service-serving-certificate-secrets