KubeVirt promises a unified compute plane for both VMs and containerized workloads, but demands a new approach to VM life cycle management and protection.

InfoWorld is a source of news, analysis, and commentary on technology trends, IT strategies, and business innovation. With a focus on enterprise technology and digital transformation, InfoWorld offers insights and guidance for IT decision-makers, software developers, and technology professionals. From  articles on cloud computing and cybersecurity to product reviews and industry trends, InfoWorld helps readers navigate the complexities of modern IT environments and make informed decisions to drive business success.

InfoWorld

As organizations migrate away from traditional hypervisors toward Kubernetes-native virtualization using KubeVirt and CDI, they face a fundamentally different approach to VM data protection. Unlike traditional hypervisors with mature, predictable backup semantics, KubeVirt defines VMs as Kubernetes custom resources (VirtualMachine, VirtualMachineInstance, DataVolume) managed declaratively via YAML. Storage is handled through CSI drivers, which vary widely in snapshot capability, complicating consistent multi-disk backups. KubeVirt snapshots capture VM spec and PVC volume snapshots but do not preserve memory state or provide application consistency without custom hooks. Cross-cluster recovery adds further complexity due to heterogeneous StorageClasses. Tools like Velero and CloudCasa bypass KubeVirt's native snapshot mechanism, instead directly backing up custom resources and orchestrating CSI snapshots for off-cluster portability. Architects and platform engineers must adopt new skills, assumptions, and Kubernetes-specific DR tooling.

Rethinking VM data protection in cloud-native environments