Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2094891

Summary:	[IBMCloud] Private Clusters Require DNS CRN in PlatformStatus
Product:	OpenShift Container Platform	Reporter:	Christopher J Schaefer <cschaefe>
Component:	Installer	Assignee:	aos-network-edge-staff <aos-network-edge-staff>
Installer sub component:	openshift-installer	QA Contact:	MayXu <maxu>
Status:	CLOSED NOTABUG	Docs Contact:
Severity:	high
Priority:	unspecified	CC:	aos-bugs, hongli, jnowicki, maxu, me, mfojtik, rgangwar, rvanderp
Version:	4.11	Flags:	maxu: needinfo-
Target Milestone:	---
Target Release:	4.12.0
Hardware:	All
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-08-17 15:16:56 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Christopher J Schaefer 2022-06-08 14:45:19 UTC

Description of problem:
Support for DNS on IBM Cloud IPI requires a change to the cluster PlatformStatus, requiring a new field for the DNS CRN that will be used by the IngressOperator

Version-Release number of selected component (if applicable):
4.12 (this new feature request is planned for the 4.12 release)


How reproducible:
100%

Steps to Reproduce:
1. Create install-config.yaml, and set publishStategy to Internal
2. Create cluster
3. Installer and IngressOperator are not able to properly set the PlatformStatus to support IBM Cloud Internal clusters.

Actual results:
Neither the Installer nor the IngressOperator is able to access/set a DNS CRN value in the PlatformStatus. A new field is required to flag that the IngressOperator should use DNS rather than CIS (which is the only available field at this time) to complete the necessary configuration.

Expected results:
Installer sets the DNS CRN in the cluster-config (infrastructure/cluster), which the IngressOperator can use to complete configuration and create then necessary DNS resources for the cluster during bring up.


Additional info:
IBM Cloud has already created a PR to add this support to the openshift/api, which can then be pulled down into the necessary components (IngressOperator, Installer, etc.)
https://github.com/openshift/api/pull/1154

Comment 1 MayXu 2022-06-23 02:27:26 UTC

@rgangwar , could you help set the target version of the bug, thanks

Comment 2 Rahul Gangwar 2022-06-23 04:29:57 UTC

@hongli could you help set the target version of the bug, thanks

Comment 3 Hongan Li 2022-06-23 04:33:47 UTC

looks it is for 4.12, but currently no 4.12 in the target release. so let's set it later

Comment 5 Jeff Nowicki 2022-07-05 13:06:00 UTC

This fix is in 4.12 and will not be cherry-picked back to 4.11. Please verify/close on 4.12.

Comment 6 MayXu 2022-07-20 07:11:49 UTC

waiting for https://github.com/openshift/installer/pull/6056 merged.

Comment 7 Christopher J Schaefer 2022-08-11 16:25:21 UTC

@maxu I see that https://github.com/openshift/installer/pull/6056 is marked as invalid since this BZ is `ON_QA` and not in an acceptable state.
https://github.com/openshift/installer/pull/6056#issuecomment-1189320454

Can this be changed to one of those states, or should this BZ be closed as resolved and I remove the BZ reference in that PR?