When NASA's Jet Propulsion Laboratory decides to overhaul its mission-critical IT infrastructure, the choice of platform is not a routine procurement decision. JPL is the organization responsible for some of the most demanding computational workloads in human history, from managing interplanetary spacecraft to processing telemetry from the edges of the solar system. The infrastructure it runs on has to be as reliable as the missions it supports.

[For more news, click here]

That makes the laboratory's decision to migrate to Red Hat OpenShift Virtualization a story worth paying attention to, not just for what it says about JPL, but for what it says about where enterprise IT is heading more broadly.

From Legacy VMs to a Unified Hybrid Cloud Platform

The migration centers on Red Hat OpenShift with its built-in OpenShift Virtualization capability, which gives JPL a single platform capable of managing both existing virtual machine workloads and future containerized applications. That combination, VM management and container-native infrastructure under one roof, solves a problem that has quietly become one of the more expensive headaches in enterprise IT: the operational gap between legacy virtualization environments and modern cloud-native architectures.

For most organizations, those two worlds have historically required separate toolchains, separate teams, and separate operational logic. The result is fragmentation: infrastructure costs that compound over time, skill gaps that widen as teams are asked to maintain two parallel operating models, and a ceiling on how quickly new applications can be brought to production.

JPL's approach collapses that gap. By running VMs directly on OpenShift, the laboratory can use cloud-native tooling, including pipelines for VM creation and management, to streamline day-to-day operations while building on a foundation that is ready for containerized workloads as they evolve. It is an infrastructure strategy that prioritizes forward compatibility without discarding the existing investment.

Security at the Platform Level, Not Bolted On

For an organization like JPL, security is not a feature. It is a non-negotiable operating condition. The laboratory handles classified research, manages active deep-space missions, and operates within the federal compliance landscape. Any platform running its core infrastructure has to meet a standard that most commercial environments would consider exceptional.

Red Hat OpenShift addresses this at the platform layer rather than through third-party add-ons. Virtual machines running on OpenShift inherit the enterprise-grade security architecture of the platform itself, including robust network policies, role-based access control, and automatic SELinux security contexts. Layered on top of that foundation are the compliance operator and Red Hat Advanced Cluster Security for Kubernetes, which together provide multi-layered security capabilities across build, runtime, and cluster operations.

That architecture matters because it means security is consistent and enforceable across the entire environment, not dependent on individual administrators remembering to apply the right configuration to each workload. For a laboratory operating at JPL's scale and complexity, the difference between security that is baked into the platform and security that has to be manually maintained is the difference between a manageable posture and a permanent vulnerability.

What This Move Signals for the Broader Hybrid Cloud Conversation

JPL's migration is a data point in a larger pattern that has been building across enterprise IT for the past several years. Organizations that built significant virtualization estates during the VMware era are now revisiting those commitments, driven by a combination of cost pressure, licensing changes, and a genuine desire to modernize without a wholesale rip-and-replace.

Red Hat OpenShift Virtualization has emerged as one of the more credible destinations for that transition, precisely because it does not ask organizations to abandon their existing VM investments immediately. The path is incremental: run your VMs on OpenShift today, migrate workloads to containers at the pace that makes sense for the business, and build toward a hybrid cloud foundation that works consistently across on-premise and cloud environments.

Sachin Mullick, Director of Product Management for Hybrid Platforms at Red Hat, articulated the logic directly: "Organizations today are grappling with the need to advance their digital capabilities while maximizing the value of their existing application investments. With Red Hat OpenShift Virtualization, customers can simplify VM migration and management while taking advantage of built-in automation to reduce operational complexity. Red Hat provides the flexibility, confidence and operational efficiency to help our customers meet their evolving mission goals."

That framing resonates beyond the government sector. Across financial services, healthcare, manufacturing, and telecommunications, the same tension exists: enterprises have built substantial infrastructure on virtualization platforms and cannot simply migrate everything overnight, but they also cannot afford to run separate modernization tracks indefinitely. A platform that bridges both worlds without forcing an either-or decision is increasingly the more pragmatic choice.

The Open Source Dimension

There is a dimension to this story that deserves more attention than it typically receives in coverage of enterprise infrastructure decisions. JPL's choice of Red Hat is, at its core, a choice of open source. Red Hat OpenShift is built on Kubernetes, the open source container orchestration platform that has become the de facto standard for cloud-native infrastructure. OpenShift Virtualization itself is built on KubeVirt, an open source project that extends Kubernetes to run VM workloads natively.

For a government-funded research laboratory operating in an environment where long-term vendor independence matters, that open source foundation carries real strategic value. It means JPL is not locked into a proprietary virtualization stack that can change pricing, licensing terms, or support policies at a vendor's discretion. The underlying technology is transparent, auditable, and supported by a broad community of contributors beyond any single company.

That consideration is becoming more explicit in public sector infrastructure decisions globally, and JPL's migration reflects it directly.

The announcement comes as Red Hat continues to expand its OpenShift ecosystem across sectors where infrastructure reliability and security are primary requirements. For JPL, which has spent decades pushing the boundaries of what is physically possible in space exploration, having an IT infrastructure that can keep pace with the demands of that mission is not a background concern. It is as fundamental as the spacecraft themselves.

Related Articles:

SAP Research Reveals UAE Enterprises Are Betting on ERP, Not Standalone AI Tools, to Scale Intelligence Across Operations

8,000 Jobs. $115 Billion in AI Spending. Meta's Workforce Gamble Signals a Tech Reckoning

SUSE Expands Oracle Partnership, Bringing Its Full Portfolio to OCI Marketplace