We are reevaluating our virtualization platform because VMware pricing is roughly four times higher than OpenShift, and our current hardware is only partly supported by the newer VMware release. Nutanix is no longer being considered because its renewal pricing was even higher, while other alternatives have been rejected by leadership as not mature enough.
Our environment is about 95% virtual machines, with roughly 75% Linux-based workloads, including Oracle databases and RHEL application servers. Most applications are web-based, and we rely on disaster recovery features such as Site Recovery Manager. The team has little Kubernetes experience, although OpenShift is being considered because of its lower cost. Management is hesitant to adopt Kubernetes, and the team is unsure whether moving to OpenShift would be practical.
I am trying to understand whether OpenShift is a realistic VMware replacement for this environment, or whether we should focus on another hypervisor and plan a gradual modernization. What approach would you recommend?
5 Answers
For a straightforward hypervisor replacement, Proxmox is worth evaluating seriously. It uses mature KVM virtualization, supports Linux and Windows guests, and can provide clustering, storage, backups, and high availability without VMware-level licensing costs. There is still a learning curve, and you would need to validate hardware, backup, monitoring, and disaster-recovery procedures, but a pilot could give management concrete results instead of just a proposal.
Your unsupported hardware is a problem regardless of which platform you choose. Before making the product decision, build a hardware compatibility and refresh plan. Also compare the complete three- to five-year cost: licenses, support, storage, backup, DR, migration work, training, and additional staff. A lower software price will not help if the hardware cannot run the target platform reliably.
Do not overlook disaster recovery. Site Recovery Manager is convenient, but any replacement needs a tested equivalent for replication, orchestration, failover, rollback, and recovery testing. I would run a proof of concept with representative RHEL servers, an Oracle workload, a web application, backups, and a full DR exercise. That evidence should make the decision much clearer than comparing license prices alone.
OpenShift is not a direct VMware replacement. It is a Kubernetes platform that can also run virtual machines, but operating it requires Kubernetes, networking, storage, and platform expertise. If your team is not comfortable with Kubernetes, OpenShift will probably be a much larger operational change than moving to another hypervisor. It may make sense later for containerizing suitable web applications, but I would not choose it solely as a cheaper VMware substitute.
Consider separating the decisions. Pick a supported virtualization platform for the existing VM estate, then create a separate modernization roadmap for applications that could eventually become containers. OpenShift could be useful for that second phase, especially for web workloads, but migrating databases and ordinary VMs directly into it will not automatically reduce complexity. If leadership will not approve alternatives such as Proxmox or another KVM-based platform, the practical choices may be renewing VMware temporarily or funding the skills and infrastructure needed for a larger OpenShift transition.
That is one of my biggest concerns. We would need to include a hardware refresh in the business case, not treat it as a VMware-only issue.