-
Epic
-
Resolution: Done
-
Critical
-
None
Goal
Currently, VMs are updated by using the LiveUpdateFeatures field, this leads to an inconsistent and confusing API. This epic is about retiring that field and instead implementing VMRolloutStrategy at the cluster level.
User Stories
- As a cluster admin, I would like to be able to control how changes to user's workloads are propagated so that they don't need to worry about such details.
- As a workload owner, I would like declarative changes I make to a VM to be propagated without having to restart so that my workloads are not interrupted.
Non-Requirements
- This is not about propagating every change to the VM without restart--this is about specific fields.
Notes
- Design document merged: https://github.com/kubevirt/community/pull/242
There are no Sub-Tasks for this issue.