On an environment having more that one network connection,
for a given service,  I'd like to be able to specify what is the egress source IP address as well as the physical interface where the traffic will be sent out. 
For example in the service definition we should be able to set explicitly the Egress IP address as well the device as:

• egressIP : XX.YY.ZZ.WW
• egressDEV : eth1

The result would be that IP traffic originated by the POD implementing the service and not directed towards other PODs,  is masked with egressIP as Source and statically routed through eth1.
 
With OVN, we already have the capability to specify the source IP address but not the physical interface, [0],[1],[2].
 
[0] https://github.com/ovn-org/ovn-kubernetes/blob/master/docs/egress-ip.md
[1] https://docs.cilium.io/en/v1.10/gettingstarted/egress-gateway/
[2] https://antrea.io/docs/v1.3.0/docs/egress/