Assessment and plan
An inventory of your VMs, networks and storage, sizing of the new cluster and a migration schedule.
Cloud Exit migrates VMware environments to Kubernetes with KubeVirt, on the infrastructure you choose.
€50,400 a year
VMware Cloud Foundation license fees on three hosts with 144 cores. Kubernetes and KubeVirt have no license fees.
Applications run unchanged
Each VM keeps its disks, operating system and network settings, including VLANs and IP addresses.
Copied while running
Forklift copies each VM to KubeVirt while it runs on VMware. Switchover happens in an agreed window, and the original stays until you sign off.
Your servers or rented bare metal
In-house server clusters, air-gapped environments, colocation and rented bare metal such as Hetzner.
Overview
KubeVirt runs virtual machines on Kubernetes, next to containers. Each VM keeps its disks, operating system and network settings, so applications run unchanged. We build the cluster where you need it and migrate the VMs in planned batches.
We export your vCenter inventory, map networks and storage to the new cluster and agree the order in which VMs move.
Forklift copies each VM’s disks to the cluster while the VM keeps running on VMware, and keeps them in sync until switchover.
In an agreed window the VM is shut down on VMware, the remaining changes are copied and the VM starts on KubeVirt.
You test the application. The original VM stays on VMware, switched off, until you sign off.
VMware
vCenter and ESXi
KubeVirt
Kubernetes cluster
We export your vCenter inventory, map networks and storage to the new cluster and agree the order in which VMs move.
Forklift copies each VM’s disks to the cluster while the VM keeps running on VMware, and keeps them in sync until switchover.
AGREED WINDOW
In an agreed window the VM is shut down on VMware, the remaining changes are copied and the VM starts on KubeVirt.
You test the application. The original VM stays on VMware, switched off, until you sign off.
Savings
Kubernetes and KubeVirt have no license fees. For a typical estate of three hosts with two 24-core CPUs each, 144 cores in total, these are the VMware Cloud Foundation license fees you no longer pay. Most vSphere features have a direct equivalent; the feature parity table shows where they differ.
VMs keep their disks, operating systems and network settings, and applications run unchanged. The capabilities teams use every day carry over.
Savings are VMware license fees only, based on the widely reported VCF list price of €350 per core per year; Broadcom does not publish a price list. Customers on vSphere Foundation, quoted in 2026 at €100 to €196 per core per year, save €14,400 to €28,224 a year on the same estate. Hardware and hosting are needed on either platform. Cloud Exit support and services are priced separately. Figures as of October 2026.
Engagement
An inventory of your VMs, networks and storage, sizing of the new cluster and a migration schedule.
A highly available cluster with KubeVirt, CSI storage and Cilium networking. VLANs and IP addresses carry over.
Every VM moved with Forklift in batches scheduled with your team, including conversion to VirtIO drivers.
Prometheus, Grafana and Alertmanager cover the cluster, storage and every VM, with alerts sent to your team.
VM definitions are kept in Git and applied automatically. Velero backs up the VMs and the cluster state.
Documentation, training for your administrators, and ongoing platform support after the last VM has moved.
Architecture
KubeVirt adds virtual machines to Kubernetes. Each VM runs in a pod as a QEMU process on KVM, so VMs and containers share one scheduler, storage layer and network.
VMware vSphere
vCenter manages ESXi hosts
vCenter Server
Inventory, HA, DRS, vMotion
Distributed switch, NSX
Port groups on VLANs
vSAN or VMFS
Datastores shared by hosts
Kubernetes with KubeVirt
Kubernetes manages Linux nodes, KubeVirt adds VMs
Git repository
VMs and networks as YAML
GitOps
Applies each change
Control plane
Highly available on three nodes
Cilium network
VMs keep their VLANs and IPs
Replicated storage
Local NVMe across nodes
Existing SAN or NAS
Vendor CSI driver
The same x86 servers
Both platforms run on standard hardware
Platform
On vSphere, people operate infrastructure step by step. On Kubernetes you describe what you want, your VMs and applications, and the platform does the work of making reality match it, continuously.
Every VM, network and policy is written down in Git as the state you want. No click-paths, no unrecorded changes.
Every change is a reviewed commit: who changed what, when and why. Rolling back means reverting that commit.
Kubernetes keeps reality matching your intent. Failed VMs restart elsewhere and VMs move off hosts being patched.
Kubernetes and KubeVirt are open-source CNCF projects under Apache 2.0. Nothing to renew, and it runs anywhere.
Applications move from VMs to containers one at a time, on the same cluster and the same network.
Containerised applications scale with demand and deploy with rolling updates and a quick rollback.
Kubernetes operators run databases such as PostgreSQL with automated failover, backups and upgrades.
01
The VM's CPU, memory, disks and networks are described in a manifest, stored in Git.
02
GitOps applies the manifest to the Kubernetes API, which records the VM.
03
virt-controller creates a pod for the VM, and the scheduler places it on a node with capacity.
04
virt-handler on that node starts the VM with QEMU and KVM, attached to its volumes and VLANs.
Parity
Everything marked equivalent is set up as part of the migration.
Where support is partial
Partial means the main use case needs a different tool or design. If you depend on Fault Tolerance, NSX routing and load balancing, or orchestrated disaster recovery, raise it during the assessment so the scope reflects it.
Deployment
The platform is the same wherever it runs. We deploy on your own servers, in isolated networks, or on rented bare metal, and manage every cluster the same way.
The cluster runs in your data center or colocation, on the existing VMware hosts after migration or on new servers.
For sites with no internet connection. Container images, VM images and updates are mirrored to a registry inside the network, and the cluster is installed and upgraded from there.
Dedicated servers rented monthly with no long-term contract, from Hetzner or another bare-metal provider.
On local NVMe, VMs use storage replicated across the nodes. With an existing SAN or NAS, KubeVirt uses the vendor's CSI driver, over Fibre Channel, iSCSI, NVMe/TCP or NFS.
Partner
Built on 10+ years of experience with Kubernetes, virtualization and containerization.
Experience with Kubernetes, virtualization and containerization
Dedicated engineers who love their craft
Options for 24x7 SLAs
Cost effective
Clear up-front pricing structure and agreements
01
An RVTools export or a list of hosts and VMs is enough to start. If you have a renewal quote, send that too.
02
We size the cluster and quote the migration at a fixed price.
03
VMs move on a schedule agreed with you. The originals stay on VMware until you sign off.