Most enterprises did not choose to run two infrastructures. It happened gradually. Cloud native projects landed on their own Kubernetes stack, in the cloud or on-premises, while the business applications everyone depends on stayed on virtual machines. Two platforms, two operating models, two sets of skills, two support contracts — and one IT team stretched across both.
A recent Nutanix infographic, From VMs to Containers — Run Your Work, Your Way, makes a simple argument: running VMs and containers together on a single platform removes a layer of complexity that nobody actually needs. Below is our read of it, and what it means for IT teams here in Morocco.
The hidden cost of siloed environments
Separate environments for VMs and containers look reasonable on a whiteboard. In production they quietly tax the organisation. Capacity is planned twice, so utilisation on both sides stays low. Data protection and disaster recovery are designed twice, with different tools and different recovery objectives. Security policy is written twice, and the two versions drift apart. Every incident starts with a question that should not need asking: which platform owns this problem?
There is a second, less obvious cost. Kubernetes deployed outside the virtualisation platform loses the benefits virtualisation spent twenty years perfecting — high resource utilisation, oversubscription, live migration, mature operational tooling. Teams end up rebuilding those capabilities by hand, or doing without them.
Four pillars of a unified platform
Several platforms claim to consolidate VMs and containers. They are not equal. The infographic sets out four capabilities worth checking before committing:
1. Management and monitoring
The foundation is mature, enterprise-grade virtualisation, plus a single set of tools that manages and monitors VMs and containers together. Integrated tooling is what produces genuinely unified operations — not two consoles side by side on the same desk.
2. Data services
Block, file and object storage should serve both VMs and containers from the same layer, with the same enterprise-level resiliency, data protection and disaster recovery on both sides. When container storage depends on external systems and services, the environment gets more complex, not less — and that complexity surfaces on the worst possible day, during a restore.
3. Security
Authentication, role-based access control and auditing should span both environments under one policy. Unified security is what makes operations defensible: one place to prove who can do what, and one audit trail when the question is asked.
4. Kubernetes support
Support for upstream Kubernetes on an open, complete platform, deployable in the datacenter, at the edge and in the cloud. Upstream matters: it keeps the ecosystem, the skills and the exit door open. The right unified platform should enable flexibility and choice, not trade one lock-in for another.
What consolidation actually delivers
- Eliminate silos — one platform, one operating model for traditional and cloud native applications.
- Optimise staffing needs — one set of skills to hire for and maintain, which matters in a tight talent market.
- Simplify operations — fewer consoles, fewer runbooks, fewer handoffs per incident.
- Maximise resource utilisation — containers inherit the efficiency and oversubscription benefits of mature virtualisation.
- Unify security — consistent policy and auditing across every workload.
How Nutanix approaches it
Nutanix runs applications and manages data across datacenter, edge and cloud on a single platform, combining mature enterprise virtualisation with an open, complete Kubernetes stack. Traditional and cloud native applications sit on an equal footing, supported by three things worth naming:
- Full-stack operations — one platform for Kubernetes, VMs, storage, networking and security, standardising operations across hybrid, multicloud, bare metal and edge.
- Integrated platform experience — native integrations across the Nutanix product ecosystem, so VMs and containers are managed on equal terms.
- Centralised governance — consistent data protection, security and resource management policies applied to traditional and containerised workloads alike.
Where to start
Consolidation is not a big-bang migration. In practice it starts small: pick one containerised workload currently running on its own island, move it onto the platform that already runs your VMs, and measure what changes — utilisation, backup coverage, time to recover, the number of tickets that bounce between teams. The numbers usually make the case for the next workload.
The goal is not containers instead of VMs, or VMs instead of containers. It is the freedom to run each workload the way it should run, on infrastructure that does not care which one it is.
Source: Nutanix, From VMs to Containers — Run Your Work, Your Way. More on the Nutanix cloud native approach: nutanix.com/solutions/cloud-native.
MTDS is a Nutanix partner in Morocco. To discuss consolidating your VM and container workloads, get in touch.