Bug 1874613

Summary:	IngressController resource changed from namespace-scoped to cluster-scoped
Product:	OpenShift Container Platform	Reporter:	Miciah Dashiel Butler Masters <mmasters>
Component:	Networking	Assignee:	Miciah Dashiel Butler Masters <mmasters>
Networking sub component:	router	QA Contact:	Hongan Li <hongli>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	aos-bugs
Version:	4.6
Target Milestone:	---
Target Release:	4.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-27 16:36:55 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 Miciah Dashiel Butler Masters 2020-09-01 18:14:20 UTC

Description of problem:

Recently, CRDs in openshift/api were migrated from version apiextensions.k8s.io/v1beta1 to apiextensions.k8s.io/v1.  In the v1beta1 API, the default scope is "Namespaced".  In v1, the scope must be explicitly specified.  The IngressController CRD did not specify an explicit scope, and so the CRD's scope was mistakenly changed to "Cluster".


Additional info:

This commit mistakenly changed the IngressController CRD's scope to "Cluster":  https://github.com/openshift/api/pull/720/commits/fdbff4bcb56c5263cc7b8a740a3684ca9f4ba116#diff-c43b8f4ae306bf7ac8fbdde984579af1

Comment 3 Hongan Li 2020-09-07 06:38:36 UTC

verified with 4.6.0-0.nightly-2020-09-05-015624 and passed

$ oc get crd ingresscontrollers.operator.openshift.io -o jsonpath='{.spec.scope}'
Namespaced

Comment 5 errata-xmlrpc 2020-10-27 16:36:55 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.6 GA Images), 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/RHBA-2020:4196