Bug 2014938 - Ingress operator not creating wildcard route for hypershift clusters
Summary: Ingress operator not creating wildcard route for hypershift clusters
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.9
Hardware: All
OS: All
Target Milestone: ---
: 4.9.z
Assignee: Cesar Wong
QA Contact: Hongan Li
Depends On: 2011972
TreeView+ depends on / blocked
Reported: 2021-10-18 03:27 UTC by OpenShift BugZilla Robot
Modified: 2022-08-04 22:35 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-11-22 21:47:05 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-ingress-operator pull 666 0 None open [release-4.9] Bug 2014938: Use fake dns provider with external cp topology only in IBM Cloud case 2021-11-05 13:51:56 UTC
Red Hat Product Errata RHBA-2021:4712 0 None None None 2021-11-22 21:47:18 UTC

Description OpenShift BugZilla Robot 2021-10-18 03:27:31 UTC
+++ 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"

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

Comment 6 errata-xmlrpc 2021-11-22 21:47:05 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.