VMs outlined by Kubernetes sources
The primary large distinction is in illustration. In conventional virtualization methods, a VM is outlined by an object or set of objects tightly managed by the hypervisor. Its configuration, disk information, snapshots, and runtime state are all saved in a platform-specific means, enabling constant backup semantics throughout totally different environments.
KubeVirt depends on the Kubernetes mannequin as an alternative. Digital machines are outlined utilizing Kubernetes customized sources resembling VirtualMachine, VirtualMachineInstance, and (with CDI) DataVolume, that are saved within the Kubernetes management aircraft. Their configuration is thus described declaratively in YAML, and their life cycle is managed by KubeVirt’s controllers. A VM definition in KubeVirt is subsequently not a bundle of hypervisor objects, however a set of Kubernetes sources describing compute, storage, networking, initialization, and storage volumes.
A technology of Kubernetes directors have come to understand Kubernetes’ open, declarative mannequin and YAML-based definitions, however for VM directors it could be a bit complicated at first. Extra importantly for our functions, the way in which this vital metadata is backed up and restored is totally totally different. You’ll want to make use of Kubernetes-specific instruments quite than the instruments you’ve been utilizing, and people instruments would require not less than a primary understanding of the Kubernetes management aircraft.
