1. Proposed title of this feature request
Hot Add Labels to VirtualMachines

2. What is the nature and description of the request?
When adding labels to a running VM, they are not propagated down to the virt-launcher without a restart of the VM.

This makes it less intuitive and more complex for VM admins to add or modify labels on their existing workloads.

We would like to see the ability to have a label added to a running VM be hot added and propagated down to the virt-launcher pod.

3. Why does the customer need this? (List the business requirements here)
Adding, changing or removing a label to a VM requires a restart of the VM for it to apply to the virt-launcher pod.

If you need to adjust those labels for the purpose of NetworkPolicies / MultiNetworkPolicies, you often want them to apply right away and not require a restart of potentially a large number of virtual machines.

You can take a 2 step process to edit the VM for future persistence and to then oc label or edit the virt launcher pod to add/remove a label... this does subject the VM to the policy without any restart, but its not intuitive for any VM admin.

4. List any affected packages or components.