CNV-10827 introduces the VirtualMachineClusterFlavor and VirtualMachineFlavor CRDs in the Kubevirt API. It is meant to replace Template, since Template is only available in OpenShift.

MTV should then use flavor instead of template when this new API is available. The flavor design is explained in KubeVirt Virtual Machine Flavor Proposal document.

The flavor selection process should use the following criteria:

• Operating system reported by the source virtualization platform.
• Allocated resources to find the best fit flavor, i.e. at least the same amount of resources, but not more than necessary.

If flavors are not available, MTV should try to use templates. And if templates are not available, MTV should craft a default VM spec.