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: 4.9 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" Actual results: The ingress operator never reports Available because it did not create a wildcard entry for its default ingress controller. Expected results: 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 (Moderate: OpenShift Container Platform 4.10.3 security 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. https://access.redhat.com/errata/RHSA-2022:0056