Bug 1330947 - Feature request "wildcard router" [NEEDINFO]
Summary: Feature request "wildcard router"
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: RFE
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Ben Bennett
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-27 11:04 UTC by Miheer Salunke
Modified: 2020-02-14 17:45 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-12 13:54:36 UTC
Target Upstream Version:
erich: needinfo? (misalunk)


Attachments (Terms of Use)

Description Miheer Salunke 2016-04-27 11:04:56 UTC
- Proposed title of this feature request 

Feature request "wildcard router"

- What is the nature and description of the request?  
We would like to have an option in the Router to express that all (wildcard) subdomains of a DNS domain shall be regarded as the same route. Requests for that wilcard route shall be forwarded to the same service (the service associated with that route).

We believe that the use case for this is actually quite generic: One wants to deploy some in-bound proxy component, which would "pre-process" a requests, before it is forwarded to various services identified by the sub-domain name (or other wilcard parts ?) of the URL.

Specifically, we would like to do the following: A request comes in for myproject.jenkins.myopenshift.com. This is routed to a generic "Apache+SAML module" proxy, which handles SAML tokens. On successful verification of the token, it would forward the request to a back-end service located in a separate project. The back-end service could be identified by configuration, or by convention (which is the case in our case - we simply use mod_proxy+mod_rewrite to extract the target namespace from the original url). It is important that the proxy component is running in a separate project, because the operation & configuration of that, in out case is a platform responsibility, whereas the back-end service would be in a customer's responsibility.


- Is there already an existing RFE upstream or in Red Hat Bugzilla?  
No

Comment 3 Eric Rich 2018-03-12 13:54:36 UTC
This bug has been identified as a dated (created more than 3 months ago) bug. 
This bug has been triaged (has a trello card linked to it), or reviewed by Engineering/PM and has been put into the product backlog, 
however this bug has not been slated for a currently planned release (3.9, 3.10 or 3.11), which cover our releases for the rest of the calendar year. 

As a result of this bugs age, state on the current roadmap and PM Score (being below 70), this bug is being Closed - Differed, 
as it is currently not part of the products immediate priorities.

Please see: https://docs.google.com/document/d/1zdqF4rB3ea8GmVIZ7qWCVYUaQ7-EexUrQEF0MTwdDkw/edit for more details.


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