1. Proposed title of this feature request

OVN Distributed Gateway Router: Routing between secondary OVN-Kubernetes networks

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

As a platform administrator I would like to route between two L3 segments belonging to two OVN-K secondary networks (ideally creating an OVN Distributed Gateway Router).

https://developers.redhat.com/blog/2018/11/08/how-to-create-an-open-virtual-network-distributed-gateway-router#setup_details 

The could be implemented by a CRD creating a Distributed Gateway Router within OVN.

This could also be implemented within the MultiNetworkPolicies object therefore abstracting the idea of router.

This would be used to route IP block between L3 segments of different networks and configure gateway for North/South NAT (or this already implemented by the EgressIP CRD ?). 

Corresponding feature in OpenStack is:

https://docs.openstack.org/networking-ovn/latest/admin/refarch/routers.html 

https://docs.openstack.org/networking-ovn/latest/admin/routing.html#east-west 

Corresponding feature in VMware is:

https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.2/administration/GUID-EEBA627A-0860-477A-95A7-7645BA562D62.html 

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

Currently multiple customers are requesting this feature as they are migrating out of VMware and OpenStack.

Just within my scope I can identify the following opportunities depending on this feature:

• Claranet (https://redhatcrm.lightning.force.com/lightning/r/Opportunity/0066e00001riofJAAQ/view )
• Naval Group

As we are now having secondary OVN Kubernetes networks customers are starting to use them and now requires the capability to configure gateway routers between those "private" networks.

4. List any affected packages or components.

• OVN-Kubernetes
• OpenShift Virtualization