Mouser Electronics migrates VMware to OpenShift with Portworx storage

Migration timeline and goals

Mouser Electronics Inc. is building a production OpenShift Virtualization cluster to move workloads from Broadcom’s VMware, aiming to run both containers and virtual machines on a single Kubernetes-based platform. The shift follows five to six years of using Red Hat OpenShift for containers, according to Ronald Waller, a systems engineer at Mouser.

Why data management decides success

Cost is the initial driver, but success hinges on day-two operations: backups, snapshots, migrations and monitoring. SiliconANGLE reports that enterprises leaving VMware often discover that a portable data management layer determines whether the migration sticks. Mouser selected Portworx by Everpure to abstract storage for both containers and VMs, allowing the same toolsets and skill sets to manage both workload types.

Storage setup: minutes, not days

Waller described the setup process for Portworx Enterprise as frictionless: after receiving an API key from Mouser’s storage team, he configured the operator and storage cluster via Portworx Central, and the system automated the backend setup. Storage, typically a complex task, became the simplest part of the proof-of-concept cluster.

Learning curve persists despite tooling

The learning curve remains steep for VMware administrators transitioning to Kubernetes. Waller spent about a year acquiring the necessary skills, but tools like Portworx reduce the storage portion of that curve. Portworx has also expanded its integration: it made data management native to OpenShift in May and launched new AI and VM capabilities at KubeCon this year.

How this connects to recent Kubernetes developments

Earlier Lazyfounder coverage highlighted Broadcom open-sourcing its Kubernetes VM API and Red Hat’s KubeVirt project graduating from the Cloud Native Computing Foundation with a focus on AI and confidential computing. Mouser’s production cluster demonstrates these shifts moving from prototypes to real-world infrastructure.

Portworx’s approach mirrors Broadcom’s push for cross-platform standards, but Mouser’s deployment shows enterprises are already adopting these tools to reduce dependence on legacy hypervisors.

What this means

Lazyfounder analysis — our interpretation, not reported fact.

The shift from VMware to Kubernetes-based platforms like Red Hat OpenShift is no longer just about cost—it’s about consolidating control planes for both legacy VMs and containerized AI workloads. Earlier Lazyfounder coverage shows Broadcom open-sourcing its Kubernetes VM API and Red Hat’s KubeVirt refocusing on AI and confidential computing; this story adds a real-world example: Mouser Electronics is already running production OpenShift Virtualization with Portworx handling storage abstraction. For operators, the takeaway is concrete—day-two operations (backups, snapshots, migrations) now travel across clouds and distributions, reducing vendor lock-in.

Key takeaways

• Cost savings alone won’t guarantee a successful VMware exit; enterprises need a unified data management layer like Portworx to handle storage abstraction for both VMs and containers.
• Day-two operations (backups, snapshots, migrations) are portable across Kubernetes distributions, reducing long-term vendor lock-in for teams that adopt tools like Portworx.
• The learning curve for VMware admins moving to Kubernetes remains steep, but storage setup is simpler: Mouser’s engineer configured Portworx Enterprise in minutes using an API key.
• Broadcom’s earlier open-sourcing of its Kubernetes VM API aligns with this trend, but real-world adoption—like Mouser’s—shows the market is already moving beyond standards to production use.

Related on Lazyfounder

• Red Hat Inc.
• Broadcom Inc.
• More technology news
• KubeVirt graduates CNCF, now targets AI and confidential computing
• Broadcom open-sources Kubernetes VM API, pushes for cross-platform standards