Having OVN-Kubernetes configure DHCP[v6] and RA flows on OVN to advertise the LSP addresses to virt-workloads would simplify quite a lot our binding (i.e. how we extend networking from the pod interface to the VM) requirements: 

• currently, we run a custom DHCP server in the pod to advertise the IP on the pod interface
• this is not supported in OpenShift (only is upstream)

Offloading this functionality to OVN would reduce a lot the amount of code we would need to develop for the binding.

Additional information

We are already doing this for HyperShift VMs on the default network: we check for a KubeVirt annotation on the pod, and if found, we provision DHCP flows, and do not configure the IP address in the pod interface.

We are requesting something similar (for UDN), but we would prefer if OVN-Kubernetes both:

• configured the pod interface
• configured the DHCP[v6] and RA flows

Note: We should try to come up with a better criteria for identifying when to provision these flows: this might be useful for more thank KubeVirt VMs.

Limitations:

port security is blocking non mac derived ipv6 LLAs, one possible solution is to retrieve the generated LLAs at VMs with guest agent and include them at port security from ovn-k