Bug 1720180 - Wildcard route support for OCP 4.2
Summary: Wildcard route support for OCP 4.2
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.1.0
Hardware: All
OS: All
unspecified
low
Target Milestone: ---
: ---
Assignee: Dan Mace
QA Contact: Hongan Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-13 10:27 UTC by David Hernández Fernández
Modified: 2022-08-04 22:24 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-13 14:46:18 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1660647 0 high CLOSED Wildcard routes get 503 intermittently 2022-08-04 22:20:47 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.