Skip to content

History

Origin

KubeVirt began at Red Hat in late 2016 from a single question: could a virtual machine run inside a container and be deployed by Kubernetes? The repository was created on 2016-12-16, and the project was formally launched and open-sourced in January 2017 (Red Hat: What is KubeVirt?, InfoQ). The goal was to give teams already invested in Kubernetes a way to keep VM-bound workloads without running a second platform.

Timeline

YearMilestone
2016Repository created (2016-12-16); prototyping at Red Hat
2017Formal launch and open-sourcing
2019Accepted to the CNCF Sandbox (2019-09-06)
2020Red Hat OpenShift Virtualization (KubeVirt + KVM) reaches GA
2022Promoted to CNCF Incubating (2022-04-19)
2023v1.0 released; release cadence moved to three times per year

How it evolved

The early project tracked Kubernetes closely and shipped frequently. With the v1.0 release in July 2023, the maintainers changed the release model: instead of monthly releases, KubeVirt moved to three releases per year aligned with the Kubernetes release model, signalling a shift toward stability for production users (CNCF: KubeVirt v1.0 has landed!).

The architectural through-line has been consistency with Kubernetes. The project states its guiding rule as "if in conflict, then prefer Kubernetes over Virtualization," which is why VMs run inside Pods and reuse the standard scheduler, networking, and storage rather than a parallel control plane (CNCF v1.0 blog).

Where it stands now

KubeVirt is a CNCF Incubating project (promoted 2022-04-19) and releases roughly three times per year. As of 2026-06-24 the latest release was v1.8.4 (2026-06-16). As of November 2025 the project was reported to be in the CNCF Graduation process with 41 listed adopters (CNCF projects: KubeVirt). The codebase is Go (go.mod:1, go 1.24.0) under Apache-2.0 (LICENSE:1).