1. Proposed title of this feature request

• Support EgressIP on multiple interfaces on cloud platforms

2. What is the nature and description of the request?

• There is a usage requirement for multiple interfaces being linked to multiple egressIP's to distribute traffic handling away from the primary interface on a node and enable a more stable method for EgressIP traffic management on cloud platforms. Customer use-case necessitates AWS but is seeking support for option available to bare-metal cluster instances.

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

• build OpenShift cluster on AWS EC2 instances and we have limitation of IP addresses per EC2 instance network interface.
• Objectively, mapping too many egressIP's to the existing interface will hit the network IP limitation and prevent creation of all the desired EgressIP's needed for the project.
• Secondary/additional interfaces would potentially allow to bypass this limitation.

4. List any affected packages or components.

See documentation here:

https://docs.openshift.com/container-platform/4.14/networking/ovn_kubernetes_network_provider/configuring-egress-ips-ovn.html#nw-egress-ips-multi-nic-considerations_configuring-egress-ips-ovn

~~~
If the egress IP is not within the subnet of the primary network interface subnet, you can use an egress IP on another Linux network interface that is not of the primary network interface type.

...

Requirements for assigning an egress IP to a network interface that is not the primary network interface
For users who want an egress IP and traffic to be routed over a particular interface that is not the primary network interface, the following conditions must be met:

OpenShift Container Platform is installed on a bare metal cluster. This feature is disabled within cloud or hypervisor environments.
~~~

See maximum cloud IP segment calculation here:

~~~
IP capacity = public cloud default capacity - sum(current IP assignments)
~~~