JPL shifts mission systems to OpenShift platform

NASA’s Jet Propulsion Laboratory has moved mission-critical IT infrastructure to Red Hat OpenShift Virtualization, strengthening the computing foundation behind deep space operations as robotic missions place rising demands on data handling, resilience and automation.

The migration gives JPL a unified platform for running traditional virtual machines alongside containerised applications, allowing teams to modernise core workloads without forcing an abrupt break from legacy systems that support highly specialised mission environments. The decision positions OpenShift as part of a broader operational shift inside space agencies and research organisations, where hybrid cloud architecture is being used to support scientific computing, secure application delivery and long-duration spacecraft operations.

JPL selected Red Hat OpenShift with built-in virtualisation capability to support a high-performance environment designed for complex mission workloads. The platform enables virtual machine migration and management while providing a consistent foundation for future cloud-native applications. That combination is significant for a laboratory whose systems must support mission planning, spacecraft data processing, telemetry handling, software development and operational continuity across projects that can run for years or decades.

The laboratory, federally funded by NASA and managed by the California Institute of Technology, is central to the United States’ robotic exploration programme. Spacecraft developed at JPL have flown to every planet in the solar system and beyond, while its teams support missions spanning Mars, Jupiter, Earth science, asteroid exploration and deep-space communications. Its operational environment is therefore unusually sensitive to downtime, software fragmentation and infrastructure complexity.

A key part of that workload is the Deep Space Network, the global communications system managed and operated by JPL’s Interplanetary Network Directorate. Its complexes in California, Spain and Australia provide continuous communications coverage with spacecraft as Earth rotates. The network supports interplanetary missions, radio astronomy, radar astronomy and selected Earth-orbiting missions, making reliability and scheduling efficiency central to mission success.

The OpenShift deployment comes as deep-space operations are being reshaped by heavier data flows and more demanding spacecraft instruments. Missions such as Europa Clipper, launched in 2024 and due to reach Jupiter in 2030, require long-term operational planning, radiation-tolerant hardware, repeated flybys and extensive science data management. JPL also supports missions such as Psyche, Mars rover operations and Earth observation programmes that add to the pressure on mission systems.

OpenShift Virtualization allows organisations to run virtual machines on Kubernetes-based infrastructure, reducing the divide between established applications and newer container-based services. For JPL, that means existing workloads can remain operational while development teams gain a path to automation, microservices and AI-ready application patterns. The model is designed to avoid the operational risk of replacing mature systems too quickly, particularly in environments where software certification, security reviews and mission continuity impose strict constraints.

Security is a major element of the platform choice. OpenShift includes role-based access control, network policy controls and SELinux security contexts, while related tools support compliance monitoring and runtime security across clusters. Such controls are important for agencies handling sensitive mission systems, scientific data and operational pipelines connected to spacecraft communications.

The move also reflects a broader enterprise technology trend. Organisations with large virtual machine estates are reassessing infrastructure strategies as they seek alternatives that can support both legacy workloads and application modernisation. Open-source platforms have gained ground where institutions want portability across data centres, private cloud and public cloud environments while retaining control over security and operations.

For Red Hat, the JPL deployment reinforces OpenShift Virtualization as more than a migration tool. The company is positioning the platform as a bridge between traditional virtualisation and cloud-native computing, particularly for organisations that cannot simply abandon established workloads. The JPL case gives that message a high-profile reference point in one of the most demanding technical environments in government science.

JPL’s operational needs are distinct from standard enterprise computing. Spacecraft missions often involve customised software, long service lives, rigorous validation requirements and interfaces with ground systems that must function across vast distances. Signals from deep-space spacecraft may take minutes or hours to travel, leaving little room for unreliable support systems on the ground. Infrastructure modernisation must therefore be incremental, secure and carefully controlled.

The migration is also aligned with the growing role of automation in mission support. Deep-space operations involve complex scheduling, telemetry processing, instrument planning and cross-team coordination. A platform that can simplify workload management, automate repeatable tasks and support consistent deployment practices offers potential efficiency gains across technical teams managing multiple spacecraft and science programmes.