1. Proposed title of this feature request
non-HTTP routers
3. What is the nature and description of the request?
The OSE3 model provides services for internal linking and routes for external linking. At the moment, only HTTP is supported for routes. This prevents us from exposing things like a database or a remote EJB or other binary connection.
4. Why does the customer need this? (List the business requirements here)
In our multi-tenant setup, we need to decide which functionality to expose to the world/other tenants. We aim to standardize on HTTP, but this is not always possible (especially when migrating legacy systems). Allowing loadbalanced routes to these binary ports adds a value.
5. How would the customer like to achieve this? (List the functional requirements here)
* the HAproxy used for the routers at this moment is capable of handling TCP, so the configuration generated for it should cope with non-HTTP traffic
6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
* create a route for a remote EJB
7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
What information can you provide around timeframes and urgency?
8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
Openshift 3.2
10. List any affected packages or components.
Openshift 3.x
11. Would the customer be able to assist in testing this functionality if implemented?
Yes.
Our recommendation is to use Service NodePorts with the product today for this function. Our documentation should describe how to make service node ports HA by leveraging the same mechanisms the routers use to be HA.
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, 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-2016:1933
1. Proposed title of this feature request non-HTTP routers 3. What is the nature and description of the request? The OSE3 model provides services for internal linking and routes for external linking. At the moment, only HTTP is supported for routes. This prevents us from exposing things like a database or a remote EJB or other binary connection. 4. Why does the customer need this? (List the business requirements here) In our multi-tenant setup, we need to decide which functionality to expose to the world/other tenants. We aim to standardize on HTTP, but this is not always possible (especially when migrating legacy systems). Allowing loadbalanced routes to these binary ports adds a value. 5. How would the customer like to achieve this? (List the functional requirements here) * the HAproxy used for the routers at this moment is capable of handling TCP, so the configuration generated for it should cope with non-HTTP traffic 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. * create a route for a remote EJB 7. Is there already an existing RFE upstream or in Red Hat Bugzilla? What information can you provide around timeframes and urgency? 8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)? Openshift 3.2 10. List any affected packages or components. Openshift 3.x 11. Would the customer be able to assist in testing this functionality if implemented? Yes.