Per Service Traffic Segregation

1. Proposed title of this feature request -

Per Service Traffic Segregation

1. What is the nature and description of the request? - 

• Pods have a single interface (eth0 primary interface)
• Each pod exposes a single service
• Several pods exporting the same service may be deployed on the same worker node
• For traffic segregation, each worker node has several network interfaces
• For service types of either NodePort or LoadBalancer, it must be possible to specify which interface of the worker node is used for traffic of that specific service
• Need in particular to ensure that egress traffic of a given service leaves the worker node from the interface associated to that service

• The source IP of egress packets is the IP address of the interface from which the traffic leaves the worker node

3. Why does the customer need this? (List the business requirements here) -

According to 3GPP a RAN CNF interfaces at least 3 different, independent networks, not limited to SCTP.
In order to comply to 3GPP, a CNF must be able to deploy services towards different networks.
That means the CNI must be able to tie a Service to a Network Device.
Multus can do that, but based on POD and not on Service.

4. List any affected packages or components. - Unknown