For ovs-cni to generate the veth interface name on the host to bind with the Pod

[jiayoukun]

The generated veth to the host-side ovs bridge needs to be diverted through the flow table, but the veth name is a piece of random numbers, making it an unfriendly correspondence with the Pod.
Is there a better way?
Waiting for your reply, thanks!

[cybercoder]

As far as I know, OpenFlow limits port names to 15 bytes. So It's better to attach the generated random name somewhere accessible. I have this problem with Multus and ovs cni, I can't find out which ovs port belongs to which machine.