Description of problem:

When egressIP on secondary interface is used along VRF, to have for example the default gateway in the secondary interface, the external traffic is not working because the SYN-ACK packet is routed outside the secondary interface instead of being routed to the ovn-k8s-mp0 as the clusterNetwork route is not present in the VRF table. That route cannot be added using NMState because interface `ovn-k8s-mp0` is ignored, but anyway adding the clusterNetwork route requires to know the cluster network address assigned to the egressIP node and is not sustainable at scale level.

Version-Release number of selected component (if applicable):

reproduced in 4.18 and 4.17

How reproducible:

always

Steps to Reproduce:

1. Create the VRF along with EgressIP on secondary interface.

2. Add the default route in the VRF table 

3. Test connectivity from the pod using the egressIP

Actual results:

incorrect routing at the egressIP node

Expected results:
The clusterNetwork route should be automatically added to the VRF table used by the egressIP.

Additional info:

Two possible workarounds existing:

1. Remove the VRF and add a static route in the primary route table (table id 254) for every destination network that should be reached through the secondary interface.
2. Add the route for the clusterNetwork in the VRF table.