In cri-o the first interface in a CNI result is used as the Pod.IP in Kubernetes. In net-attach-def client lib version 1.7.4, we use the first CNI result as the "default=true" interface as noted in the network-status, this is problematic for CNV along with OVN-K UDN, as it needs to know that the UDN interface is the default=true

    4.18,4.17

    Reproduction only under specific circumstances without an entire OVN-K stack.

Therefore, use: https://gist.github.com/dougbtv/a97e047c9872b2a40d275bb27af85789 in order to validate this functionality, which requires installing a custom CNI plugin using the script in the gist named 'z-dummy-cni-script.sh' create that as /var/lib/cni/bin/dummyresult on a host, and make it executable, and then make sure it's on the same node you label with multusdebug=true