Bug 1324039

Summary: [RFE] Allow creation of "redirecting routes"
Product: OpenShift Container Platform Reporter: Miheer Salunke <misalunk>
Component: RFEAssignee: Phil Cameron <pcameron>
Status: CLOSED DEFERRED QA Contact: Johnny Liu <jialiu>
Severity: low Docs Contact:
Priority: low    
Version: 3.1.0CC: aloughla, aos-bugs, atragler, erich, jokerman, mbarrett, misalunk, mleitner, mmccomas, pcameron, rkhan, sjr, sukulkar
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-12 13:54:36 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:

Description Miheer Salunke 2016-04-05 12:02:43 UTC
1. Proposed title of this feature request  
    => Allow creation of "redirecting routes"
     

 
    3. What is the nature and description of the request?  
    => We think that it would be interesting for OpenShift to cover the following user case: "As a user, I would like to be able to create a route that sends a redirect to a given URL instead of serving contents from one or more pods backed by a service".

This would, for example, ease migration of applications between different OpenShift instances (at different data centers) and/or migrate users from a OSE3 standard route to a hostname belonging to a regional load balancer, balancing among two OSE3 clusters.

Most load balancers can be configured to send a redirect instead of serving a web page under certain conditions. HAProxy is one of them. So, it should be as easy as detecting these kind of routes and setting up HAProxy config so that a redirect is sent when the hostame/path of the route is called.



    6. List any affected packages or components.  
=> router image

Comment 2 Phil Cameron 2016-08-12 20:22:11 UTC
I am starting to work on this.

Comment 3 Phil Cameron 2016-09-06 18:52:39 UTC
From Clayton Coleman email:
It's a pretty fundamental scope increase to routes, and starts to diverge significantly from ingress.  I think it needs a bit more discussion around those areas.

Comment 4 Sergi Jimenez Romero 2017-03-14 07:57:35 UTC
Phil, any updates? I noticed the trello card is blocked until ingress support has been added. Is that still the case?

Comment 5 Phil Cameron 2017-03-14 13:36:21 UTC
Still blocked as per the trello card. Not sure where this is going at this point. The concern over ingress and how it matures is still relevant.

Comment 10 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.