Goal

We are getting asks from multiple customers that would like to specify the "destination" of the VM when doing Live migration. While this may be less important in a cloud-native environment, we get this ask a lot from customers coming from other virtualization solutions, where this is common.

*This option will be enabled only to users that have permissions to list nodes in the cluster and have permissions to perform Live migration on the VM.

User Stories

• As a user with the right permissions I would like to have a simple way to specify a target node for the Live migration
• Specifying a target node should be specific only for the current migration and should not persist once the migration is done

UX doc

https://docs.google.com/document/d/1pvh9gPjIwn_xV8DOaxMdvs5dxsx3KLYTXzmHOD5awbg/edit?tab=t.0

Non-Requirements

• List of things not included in this epic, to alleviate any doubt raised during the grooming process.

Notes

• We may need to resolve conflicting configurations like that selected node does not have the resources required by the VM, or if the selected node does not comply with other configurations like affinity / anti-affinity rules, or other Node selector definitions