Goal

Now that VMRolloutStrategy is implemented, sensible fields should be allowed to update without restarting a VM. It's currently possible to update Node Affinity, but not tolerations. This would be suprising to a user as one should be able to reasonably assume these fields would behave similarly. While it's currently possible to add a toleration directly to a virt-launcher pod, this is cumbersome and breaks the workflow for the user.

User Stories

• As a workload owner I would like to be able to update tolerations for a VM on the fly, so that it can withstand taints added to a Node.

Non-Requirements

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

Notes

• Any additional details or decisions made/needed