+++ This bug was initially created as a clone of Bug #2011972 +++
Description of problem:
When running in a hypershift cluster on AWS, with controlPlaneTopology set to "External", the ingress operator does not create a DNS entry for the default ingress controller.
OpenShift release version:
How reproducible: Always
Steps to Reproduce (in detail):
1. Create a hypershift cluster with control plane topology set to "External"
2. Wait for the ingress operator to report "Available"
The ingress operator never reports Available because it did not create a wildcard entry for its default ingress controller.
The ingress operator reports available
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (OpenShift Container Platform 4.9.8 bug fix update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.