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:
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.