Platforms that run containers and full VMs side by side across clouds either run VMs inside Kubernetes using KubeVirt, run a traditional hypervisor with Kubernetes layered on top, or manage separate VM and container systems from one console. Pick by where your VMs run today and whether you want one unified runtime or one unified console. This guide compares each platform on how VMs run, which clouds each one reaches, what cloud hardware VMs require, and how VM images move in.
Disclosure: Control Plane publishes this guide.
TL;DR
The choice comes down to where your VMs run today and which execution model your team can operate.
Three models exist: VMs inside Kubernetes (KubeVirt), hypervisor-first with Kubernetes on top, and a management console over separate VM and container systems.
KubeVirt is the common engine behind most Kubernetes-native VM platforms, turning a VM into a Kubernetes pod backed by KVM.
KubeVirt VMs in public clouds need bare-metal instances or instances that support nested…