Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1700173

Summary:	[UPI on vSphere] wildcard dns entry is not added to Route53 hosted zone when creating a custom ingresscontroller
Product:	OpenShift Container Platform	Reporter:	Hongan Li <hongli>
Component:	Networking	Assignee:	Dan Mace <dmace>
Networking sub component:	DNS	QA Contact:	Hongan Li <hongli>
Status:	CLOSED NOTABUG	Docs Contact:
Severity:	high
Priority:	high	CC:	aos-bugs, eparis, mfisher, mmasters
Version:	4.1.0	Keywords:	BetaBlocker
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:		Environment:
Last Closed:	2019-04-16 16:09:16 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 Hongan Li 2019-04-16 03:43:52 UTC

Description of problem:
After fresh installing UPI on vSphere, the default wildcard route like `*.apps.gpei-vs-0415.qe.devcluster.openshift.com` has been added to Route53 and works well.
Then creating a custom ingresscontroller below:
---
kind: IngressController
apiVersion: operator.openshift.io/v1
metadata:
  name: test0
  namespace: openshift-ingress-operator
spec:
  domain: test0.gpei-vs-0415.qe.devcluster.openshift.com
---
but the new wildcard dns entry is not added to Route53 hosted zone


Version-Release number of selected component (if applicable):
4.0.0-0.nightly-2019-04-10-182914

How reproducible:
100%

Steps to Reproduce:
1. fresh install UPI on vSphere
2. create custom ingresscontroller
3.

Actual results:
wildcard dns entry is not added to Route53 hosted zone when creating a custom ingresscontroller

Expected results:
the wildcard dns entry should be added to Route53 for new custom ingresscontroller

Additional info:

Comment 4 Miciah Dashiel Butler Masters 2019-04-16 16:09:16 UTC

The ingress operator only configures Route53 if it is on AWS, because Route53 is an AWS service.  In the case of UPI on vSphere, it is the user's responsibility to configure DNS (even if the UPI happens to be AWS).

Aside from that, the ingress operator only configures DNS if the installer configures DNS zones in the dnses.config.openshift.io/cluster config.  If no zones are configured when they should be, that is an installer issue.