Add to the design document [1] an enhancement option to support the possible pod interface naming change during migration.

While we will not support this and will try to reject any attempt to do something like that, we still need a backup plan in case there will be no choice but to do support something like that (e.g. if UDN decides to drop this odd name and get back to the classic good old eth0).

The suggested solution from Vladik was to add the data to the VMI status migration section, such that the VMI controller can take it into account.
It is possible to add this in a future release because it is not dependent on the source VM. Its functionality is on the VMI controller and Migration controller.

 [1]https://github.com/kubevirt/community/blob/e65fc8a2c17f6c34579175cefd2657a0dbab4e26/design-proposals/dynamic-primary-pod-nic-name.md