Has anyone found a way to get the kubeovn Pure Underlay Networking working on the existing harvester host mgmt nic(s)? I'm trying to utilize the VPC NAT Gateway functionality here - It requires an external subnet, and the only way to attach that to an actual VLAN is the pure underly functionality. My nodes have two 10g NICs that are configured with LACP and connected to different switches for redundancy, so breaking up the bond is not an option. I've tried modifying the Provider-Network manifest to directly attach it to the mgmt-bo NIC - and using a bond NIC is supported by kubeovn But, ovs throws an error as it's in use;

# kubectl exec -n kube-system ovs-ovn-tqs8d -c openvswitch -- ovs-vsctl show
    Bridge br-uplink
        Port mgmt-bo
            trunks: [0, 3648]
            Interface mgmt-bo
                error: "could not add network device mgmt-bo to ofproto (Device or resource busy)"

It also pulls the mgmt-bo nic out of being managed by nmcli, which might create future issues if it did work. I tried attaching the ovs to the mgmt-br bridge instead of the mgmt-bo; it did not work - and the kube ovn underlay environment requirements (#5) specifies that you can't use a bridge anyway. One thing that works, but I'm exploring the implications; - Created a host network on the existing 'mgmt' cluster network (vlan tag 3648 specified) - Created underlay networks > provider network and attached to interface "mgmt-br.3648" -- which, despite the name, shows in nmcli as a "vlan" not a "bridge" - Created underlay networks > vlan, specified the vlan id as 0 (untagged), and connected to the provider network -- I expected if I tagged here, it would end up double tagged This would mean a new 'host network' is required for every pure underlay vlan, though.

Hey, we encountered the same issue when configuring the provider network with an already bonded nic. So we used another nic for the provider network. The provider network creates a bridge on the nic and it completely works fine on a unbonded nic.

I don't think it's possible - I definitely tried. Using a different NIC everything worked easily and perfectly.

Refer docs.harvesterhci.io/v1.9/networking/kubeovn-pureunderlay you need a dedicated nic for ovn pure underlay usage, the

mgmt

is for Harvester to setup, there is a network controller works upon it; if ovn works also on this network, the battle/race is something inevitable now.