-
Feature Request
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
Product / Portfolio Work
-
None
-
False
-
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
-
None
- Proposed title of this feature request
Provide a setting to route traffic for a LoadBalancer service outside the cluster
- What is the nature and description of the request?
Given a service of type LoadBalancer, it is expected that the network communication with the external IP(configured in the service) originated from the cluster nodes is routed internally to the cluster service IP as per NAT definition. However, the customer would like the option to route all traffic to the service’s external IP outside the cluster instead of routing it internally.
3. Why does the customer need this? (List the business requirements here)
This is required for applications running inside the cluster that need to be accessed from both within and outside the cluster, and where the source IP must be preserved. In customers case, the source IP must be preserved for audit purposes, and they therefore have to enable the PROXY protocol on the load balancer. Without this change, applications receive traffic using two different protocols on the same port: the original protocol for traffic coming from within the cluster, and the PROXY protocol for traffic from outside the cluster.
4. List any affected packages or components.
Both SDN and OVN .