The enterprise IT landscape is undergoing a seismic shift. Broadcom’s acquisition of VMware has left many organizations scrambling for alternatives, and Kubernetes—specifically Red Hat’s OpenShift—has emerged as a leading contender to replace traditional virtualization platforms. But the transition is far from straightforward. Ahead of the upcoming Red Hat Summit 2025, Rob Hirschfeld, CEO and Co-Founder of RackN, outlined the challenges and opportunities enterprises face as they navigate this transformation.

The VMware Exodus and Kubernetes’ Rise
Broadcom’s $61 billion takeover of VMware has triggered widespread uncertainty. Enterprises, long reliant on VMware’s virtualization stack, are now reevaluating their infrastructure strategies. Hirschfeld notes that Kubernetes, once confined to developer environments, is now seen as a strategic replacement for VMware. “Customers aren’t just asking if Kubernetes can run VMs—they’re asking how to tune, operate, and optimize their workloads at scale,” he says.

Red Hat’s OpenShift, with its integrated virtualization capabilities, has become a focal point. However, adoption isn’t without hurdles. Enterprises must rethink their approach to cluster management, storage, and networking—areas where VMware’s tightly integrated ecosystem once provided simplicity. Hirschfeld emphasizes the need for tools like Red Hat Advanced Cluster Management for Kubernetes (ACM) to streamline deployment and lifecycle management. Yet, many customers opt to deploy OpenShift clusters independently and integrate ACM retroactively, reflecting a desire for faster iteration.

The Bare Metal Imperative
A recurring theme at Red Hat Summit was the growing intersection of Kubernetes and bare metal infrastructure. Unlike cloud environments, where abstraction layers handle storage and networking, bare metal demands hands-on management of BIOS configurations, RAID arrays, and GPU orchestration. “Kubernetes was built for cloud-first workflows,” Hirschfeld explains. “On bare metal, enterprises must rebuild these abstractions themselves—a complex task requiring API-driven automation and autonomic systems.”

RackN, which specializes in bare metal automation, positions itself as a critical partner for enterprises navigating this shift. Hirschfeld highlights a key metric: while industry-standard bare metal provisioning processes often see a 20% failure rate during resets, RackN’s platform achieves 99%+ reliability. “You can’t treat bare metal like ephemeral VMs. Resilience is non-negotiable,” he adds.

Avoiding Vendor Lock-In
The rush to Kubernetes raises a paradox: enterprises escaping VMware’s lock-in risk falling into a new dependency on Red Hat. Hirschfeld advises organizations to adopt a multi-vendor strategy, building abstraction layers that allow flexibility. “Don’t let Red Hat become your new VMware,” he warns. “Use tools that enable interoperability with other Kubernetes distributions or virtualization platforms like Nutanix.”

Nutanix, while praised for its cost advantages, isn’t a seamless VMware replacement. Hirschfeld notes architectural mismatches in storage and management workflows, making full migration challenging. “Nutanix works best as a complementary solution for high-performance workloads that OpenShift can’t yet handle,” he says.

OpenShift’s Gaps and AI Ambitions
OpenShift virtualization still lags VMware in critical areas. Storage externalization, network segmentation, and VM management tools remain immature, requiring enterprises to adopt incrementally. “Early adopters are migrating non-critical workloads, but full parity will take years,” Hirschfeld acknowledges.

AI further complicates the equation. While Red Hat focuses on empowering developers with AI/ML libraries, enterprises must also optimize bare metal infrastructure for GPU clusters and large-scale training workloads. “AI isn’t a cloud-native workload. It demands deep integration with hardware—and that’s where OpenShift’s bare metal capabilities will be tested,” Hirschfeld says.

The Path Forward
Hirschfeld’s advice for enterprises is clear: prioritize agility over perfection. “Move fast, iterate, and don’t force developers to double as infrastructure experts. Treat OpenShift virtualization as a dedicated platform for virtualization teams, not an extension of your DevOps pipeline.”

Red Hat Summit underscored a broader trend: the line between infrastructure and application development is blurring. As Kubernetes evolves from a container orchestrator to a full-stack infrastructure platform, enterprises must balance innovation with operational pragmatism. For now, the VMware exodus continues—but the future belongs to those who build adaptable, hybrid environments.

Guest: Rob Hirschfeld (LinkedIn)
Company: RackN (Twitter)
Show: KubeStruck