Goal

Let users clone VMs with their mac address from one namespace to another.

User Stories

• As a VM owner, I'd like to create a clone of my VM in another namespace that I own. I'd like to keep the original mac address, so that the guest operating system is not affected. I am going to avoid mac collision in my network by stopping the original VM or connecting it to a different subnet.
• As a cluster admin, I'd like to tell which are the colliding VMs so that I can mitigate related effects. This information does not have to be synchronous: I am fine with having a documented tool that lists the offending VMs. As a stretch goal, I'd be happy to have an alert firing if my cluster has a collision.

Non-Requirements

Notes

• I have a vague memory that we have a special handling of something similar when we restore a VM twice from the same snapshot. Please see if the two flows can be united.
• For those who don't want to be blocked by KMP during the dev process of cross-namespace live migration - there is a built-in workaround on kubemacpool to have it ignore MAC duplications, which is done per namespace (see U/S docs on how to opt out the VMs webhook on your namespace). The proposed workaround is to opt out the target ns.