Additional Network and Metallb cannot use same network

When Source POD has an additional interface of type ipvlan created on ens224.xxx and this source POD is trying to access a metallb IP from same subnet as ens224.xxx. This metallb IP is being announced by speaker hosted on same node as the node where source POD is hosted. The destination POD is also hosted on same node. OVN routingViaHost is enabled. Connection fails in this scenario.

It would be better to mention this in the documentation that there is a limitation of using same vlan for both metallb and additional network.

4.13

Always