@NocturnalDanger Take a look at meshbr0. When I deployed an IncusOS cluster (using Operations Center), this network was created automatically together with the internal project intended for management containers for services such as OVN, Linstor and Ceph.
Normal bridge incusbr0 with NAT does not provide a direct connectivity for containers located on different cluster members, so ovn-central services would not be able to talk to each other directly. Using host IPs and port forwarding is possible (I did that with lots of help from AI assistents), but not easy as ovn-central, by default, tries to create network listeners for RAFT ports on the addresses of OVN cluster members, and fails if these are host IP addresses.
Note that meshbr0 uses only IPv6 SLAAC addresses, so OVN (and other services) need to be configured using IPv6 addresses.
Alternatively, management containers such as ovn-central can be connected directly to the host network.