KubeVirt Outlines Future Development, Focusing on Hardware Integration and Ecosystem Growth

KubeVirt's Core Mission and Ecosystem Expansion

KubeVirt, initiated by Red Hat in 2016, allows Kubernetes to run virtual machines alongside containers. This enables users to integrate legacy workloads with modernized applications on a single platform. Since its v1.0 release, KubeVirt has seen adoption by other projects, demonstrating its role in a broader ecosystem.

Projects like Open Sovereign AI Cloud (OSAC) utilize KubeVirt for VM, cluster, and bare-metal services. Cluster API Provider KubeVirt (CAPK) uses KubeVirt VMs as Kubernetes nodes, and Flight Control runs virt-launcher on edge devices without the full KubeVirt control plane.

Community Growth and Project Graduation

KubeVirt is currently a CNCF incubating project with contributions from companies including Nvidia, Microsoft, AMD, Intel, and SUSE. The community is actively working towards KubeVirt's graduation as a full CNCF project. The enhancement trackers for upcoming versions (v1.8, v1.9, v1.10) show a significant increase in development activity, with v1.9 alone including dozens of new proposals.

The KubeVirt Enhancement Proposal (VEP) process manages this growth by prioritizing design before code, using a single tracker, and assigning ownership to Special Interest Groups (SIGs) to maintain core stability.

Enhanced Hardware Integration and Resource Allocation

Future KubeVirt releases will focus on improved device and new hardware support. GPUs can already be claimed through Kubernetes Dynamic Resource Allocation (DRA), a beta feature in v1.9, replacing device-plugins. This claim model is being extended to generic host devices, network devices like SR-IOV, and CPUs.

The goal is for a VM to request a GPU, NIC, and CPUs, with Kubernetes allocating them as a coordinated set. Work is also underway to allow KubeVirt to build these claims from the VM specification and vendor policy, reducing the need for users to manually write ResourceClaim objects. This aligns with KubeVirt's principle of preferring Kubernetes-native solutions.

Future Development Areas

Key areas shaping KubeVirt's next releases include devices and new hardware integration, extending KubeVirt's functionality without expanding its core, confidential VMs for enhanced security, using VMs as sandboxes, and developing pluggable virtualization stacks. These initiatives aim to broaden KubeVirt's capabilities and adaptability within the Kubernetes ecosystem.