Bug 2011972 - Ingress operator not creating wildcard route for hypershift clusters
Summary: Ingress operator not creating wildcard route for hypershift clusters
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.9
Hardware: All
OS: All
medium
medium
Target Milestone: ---
: 4.10.0
Assignee: Cesar Wong
QA Contact: Hongan Li
URL:
Whiteboard:
Depends On:
Blocks: 2014938
TreeView+ depends on / blocked
 
Reported: 2021-10-07 20:03 UTC by Cesar Wong
Modified: 2022-08-04 22:35 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: The cluster ingress operator will not create wildcard DNS records for ingress controllers when the cluster's ControlPlaneTopology is set to External. Consequence: In hypershift clusters where the ControlPlaneTopology is set to External and the Platform is AWS, the cluster ingress operator never becomes available. Fix: Limit the disabling of DNS updates only for the case in which ControlPlaneTopology is External and Platform is IBMCloud. In that case, DNS is managed externally. Result: Wildcard DNS entries should get created for Hypershift running on AWS.
Clone Of:
Environment:
Last Closed: 2022-03-10 16:18:05 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-ingress-operator pull 659 0 None open Bug 2011972: Use fake dns provider with external cp topology only in IBM Cloud case 2021-10-07 20:04:54 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:18:31 UTC

Description Cesar Wong 2021-10-07 20:03:35 UTC
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

Comment 6 errata-xmlrpc 2022-03-10 16:18: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 (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


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