Kubermatic Virtualization VM Migration
Overview
Move your first production VM onto Kubermatic Virtualization (KubeV). We build and harden a production-grade KubeV platform on your hardware, with observability, alerting, backup and a tested restore, then migrate and cut over one of your application VMs (Ubuntu or Windows) within an agreed downtime window. You get a repeatable runbook and wave plan for the rest of your estate.
Goal
A production KubeV platform your team operates independently, your first application VM running on it, and a proven method to migrate the remaining estate.
Who it is for
Teams that have chosen KubeV as their virtualization platform, or completed a Proof of Value, and are ready to start moving production workloads.
Content
- 01
Design validation and sizing
Topology, sizing, source assessment and go-live criteria.
- 02
Platform installation
Production KubeV with etcd quorum across failure domains.
- 03
Networking, isolation and storage
VPC, subnets, IPAM, VLANs and live-migration-ready storage.
- 04
VM operations
Lifecycle, live migration and host-failure recovery.
- 05
Migration preparation and wave planning
Mappings, cutover and rollback plan.
- 06
Migration and cutover
Your application VM moved within the agreed window.
- 07
Hardening, backup and restore
Production checklist, backups, restore test and alerting.
- 08
Lifecycle validation
A full platform upgrade with your VM running.
- 09
Operational readiness
Documentation, enablement and go-live review.
Typical Activities
- Sizing and hardware bill of materials from the KubeV Sizing Tool
- Production hardening against Kubermatic's production checklist
- Backup of platform state and VM volumes, with a timed restore test
- Alerting routed to your channel and verified with a test condition
- Network and storage mapping, disk import and guest preparation
- Cutover with a documented rollback plan, validated by the application owner
- VM create, migrate and delete campaign to prove stability and clean teardown
- Wave planning for the remaining estate, grouped by application dependency
Deliverables
| Area | What you receive |
|---|---|
| Design and sizing | Topology, sizing record, hardware bill of materials, frozen go-live criteria |
| Platform | Hardened, HA KubeV installation with Git-managed configuration |
| Networking and storage | Configured networks and isolation, live-migration-ready storage, as-built docs |
| Migration | Your application VM migrated and accepted, cutover and rollback plan, repeatable runbook |
| Resilience | Live migration and host-failure results |
| Backup and upgrade | Backup configuration, documented restore test, documented upgrade cycle |
| Operations | Operations documentation, enablement, signed go-live readiness review |
Prerequisites
- Hypervisor hosts racked and powered, with VT-x or AMD-V enabled
- Host OS installed (Ubuntu 24.04 LTS or agreed alternative)
- Storage backend with ReadWriteMany or Block volume mode, plus a backup target
- VLANs trunked to every host, LACP/MLAG and out-of-band management
- IP addressing and firewall rules in place
- VPN or jump host access and a shared Git repository
- Admin access and VM inventory for your source environment
- Application VM selected, owner named, dependencies documented, downtime window agreed
- A KubeV production subscription
Why this Accelerator?
- A real production move, not another test.
- Safe cutover: rollback stays available until the application owner signs off.
- Day-2 proven up front: restore, upgrade and host failure tested before go-live.
- A blueprint for the estate: runbook and dependency-based wave plan.
- Your team owns it, with the docs and skills to run the platform and migrate on.
What's not included
Migration beyond one application VM, application changes or containerization, in-guest administration and licensing, 24/7 operations, multi-site rollout, physical infrastructure, fabric routing and source platform decommissioning. The KubeV subscription is contracted separately.
Optional extensions
Further migration waves, multi-region rollout, KKP on KubeV, KubeLB, GPU or SR-IOV, and managed 24/7 operations.