Bug 1720180

Summary:	Wildcard route support for OCP 4.2
Product:	OpenShift Container Platform	Reporter:	David Hernández Fernández <dahernan>
Component:	Networking	Assignee:	Dan Mace <dmace>
Networking sub component:	router	QA Contact:	Hongan Li <hongli>
Status:	CLOSED NOTABUG	Docs Contact:
Severity:	low
Priority:	unspecified	CC:	aos-bugs
Version:	4.1.0
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-13 14:46:18 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 David Hernández Fernández 2019-06-13 10:27:29 UTC

Description: 
-Wildcard route support for OCP 4.2
-Goal: Enable admins to specify a wildcard route policy through the ingress operator API.
-Problem: By default, wildcard routes are allowed and the ingress operator API provides no means to specify a wildcard route policy.
Why is this important: Shared hosting environments may want to prevent users from claiming large route domain segments.

Version-Release number of selected component (if applicable): OCP 4.2

Additional info:
https://bugzilla.redhat.com/show_bug.cgi?id=1660647 =» Not going to support wildcard routes in 4.1.
https://jira.coreos.com/browse/PROD-1098 =» Aiming wildcard route in 4.2

Comment 1 Dan Mace 2019-06-13 13:42:20 UTC

For some reason the RFE component isn't appearing, otherwise I would re-assign this as an RFE. It's already tracked as https://jira.coreos.com/browse/PROD-1098 and filing a 4.2 bug doesn't seem to serve any purpose. Can we close this?

Comment 2 David Hernández Fernández 2019-06-13 14:46:18 UTC

Hi Dan,

Yes, we could close it. I just misunderstand the workflow since I am still getting into it.