Goal

Currently all Live Migrations in KubeVirt happen with equal priority, but some migrations are more important/critical than others. For instance, a node-drain (e.g. during system upgrade) must complete or the cluster cannot finish upgrading. Other migrations, e.g. triggered from a hot plug, could happen at any time.

The idea is to create a priority queue to give preferential treatment to some migrations, with the goal that user-initiated migrations cannot choke administrative tasks.

User Stories

• As a cluster admin, I want critical migrations to occur first, such that a user cannot create a denial-of-service effect with migrations.

Non-Requirements

• This API will not be exposed to users as part of this epic. Workload owners will not be given an option to "score" their migrations to make them more/less important.

Notes

• N/A