VM landscape & suitability assessment
Structured analysis of VM workloads and evaluation of which paths make sense – including OpenShift Virt and Harvester as reference platforms.
Container. Open Source. Solutions.
Virtualisation with KubeVirt
VMware licences are rising, platforms grow uncontrolled – a consolidated operating model becomes necessary. We guide the migration to KubeVirt with a clear target architecture and a controlled migration path. Learn more
Are you operating cost-intensive infrastructure silos for virtual machines and containers?
Separate technology stacks tie up unnecessary resources and double licensing costs. We unite legacy VMs and Cloud-Native workloads on a centralised, Kubernetes-native operating model.
How you notice this in daily operations
- VMware dependency and rising licence costs
- Unclear prioritisation: what to migrate, what to keep, what to replace?
- Missing standards for hybrid workloads (policies, backup, observability)
- Separate operating models for VM and container (teams, processes, governance)
- Uncertainty around performance, storage, networking, and isolation
What we deliver
Target architecture hybrid (VM + container)
Target state for platform, network, storage, observability, and operational boundaries – storage import with CDI, networking with Multus.
Modernisation roadmap
Prioritised roadmap with delivery stages and clear dependencies instead of big-bang.
Security & governance
Role model, policies, isolation, and standards for hybrid workloads.
Operating model (incl. backup/DR)
Operations concept with clear responsibilities, runbooks, and recovery strategy.
Decision basis
Options, trade-offs, and recommendations: consolidate, migrate, or run in parallel.
Frequently asked questions
When does a KubeVirt migration make sense?
A KubeVirt migration makes sense when VMware dependency, licensing costs, or separate operating models need to be reduced strategically. Not every VM needs to move immediately: a staged approach is often safer, with workloads assessed by criticality, dependencies, and operational requirements. The result is a realistic migration path instead of a risky big bang.
Which platforms are suitable for KubeVirt?
KubeVirt can run on Kubernetes-based platforms when networking, storage, security, and operations are designed together. OpenShift Virtualization and Harvester are typical reference platforms, and other Kubernetes distributions can also be suitable. The runtime alone is not enough; the operating model for VM and container workloads matters.
What matters for storage and networking?
VM workloads have different requirements for persistence, performance, and network isolation than many container workloads. Storage import with CDI, Multus for additional networks, and clear backup/recovery processes are central building blocks. Performance profiles, dependencies, and recovery requirements should be visible before migration starts.
How is a controlled migration path defined?
A controlled migration path starts with a structured assessment of the VM landscape. Workloads are prioritised by technical suitability, risk, modernisation potential, and operational dependencies. This produces a roadmap with pilot workloads, decision rules, and clear criteria for migration, replacement, or parallel operation.
Outcome
A consolidated platform architecture with reduced dependency, clear standards, and a realistic modernisation path – without unnecessary vendor lock-in.
All results are documented and prepared so that teams can continue operating the platform independently.
More Services
Cloud-Native Platforms
Platform blueprint, GitOps setup, observability and DR strategy – with clear standards and an operable outcome.
Security & Architecture
Zero trust, policy frameworks and compliance integration for cloud-native and hybrid platforms in Switzerland.
Internal Developer Platforms
Self-service, golden paths and standards for delivery with less operational friction.
Next steps
In the virtualisation review we analyse your current situation and define a controlled migration path to KubeVirt.