-
Bug
-
Resolution: Done
-
Normal
-
None
-
4.17, 4.18, 4.19, 4.20, 4.21
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
From https://issues.redhat.com/browse/OCPBUGS-61795?focusedId=28150879&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-28150879:
In the doc it is mentioned that "Routes associated with the egress interface are copied from the main routing table to the routing table that was created to support EgressIP, as shown above. If the interface is enslaved to a VRF device, routes are copied from the VRF interfaces associated routing table."
However it looks like we don't support VRF as per bug https://issues.redhat.com/browse/OCPBUGS-51323
So in our docs for the configuring EIP on a seconday interface, can we please mention the "Routes associated with the egress interface are copied from the main routing table to the routing table that was created to support EgressIP"
Also mention that it is admin responsibility to configure the nic with the routes properly with a gateway present in the main routing table.
For example default via <gw> dev <if> for the seconday nic before OCP installation as after installation we don't support adding such configurations for OVNKubernetes as it is not tested by us.
- links to