-
Feature Request
-
Resolution: Unresolved
-
Major
-
None
-
openshift-4.16, openshift-4.18
-
None
-
Product / Portfolio Work
-
None
-
False
-
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
-
None
1. Proposed title of this feature request
Add support of proxy-protocol per route with egress operator
2. What is the nature and description of the request?
We would like to use haproxy PROXY protocol https://www.haproxy.com/documentation/haproxy-configuration-tutorials/client-ip-preservation/enable-proxy-protocol/ so that the client IP is forwarded to the application. Today this is only supported globally and in specific cases through https://access.redhat.com/solutions/6337981, it is not practical when not using HostNetwork or NodePortService.
We would like the product to be enhanced with a new annotation, for example setting haproxy.router.openshift.io/send-proxy=true on a route, would let users define a passthrough route where the client IP is not lost.
3. Why does the customer need this? (List the business requirements here)
Some of our routes are configured in "passthrough" mode. When the endpoint receives the traffic, it can only retrieve the IP of the ingress router pod, but the client IP that made the request is lost. Due to security constraint on one of our applications who would like to use passthrough route and still know which IP made the request.
4. List any affected packages or components.
HAProxy
- is related to
-
NE-552 Draft proxy-protocol enhancement proposal
-
- Closed
-