Validated 5G Core Model Cuts Integration Work for Carriers
The released model runs Ericsson 5G Core on Red Hat OpenShift and HPE hardware, a deployment framework rather than a documented general-availability product.
Updated on Nov. 3, 2026 in Data Centers
HPE, Red Hat and Ericsson released a validated deployment model that runs Ericsson dual-mode 5G Core on Red Hat OpenShift and HPE infrastructure. The model is a released, validated deployment framework, not a product that is documented here as generally shipping, and the source provides no pricing or general-availability dates.
Why it matters
The model follows a joint validation environment HPE and Ericsson established in October 2025, and it reflects a broader move toward pre-validated, cloud-native stacks for telecom core networks. It targets the integration work that has often slowed service providers' transition from infrastructure design to running 5G Core in production.
The integrated stack combines Ericsson dual-mode 5G Core network functions with Red Hat OpenShift's Kubernetes-based cloud platform on HPE ProLiant Compute and networking hardware. The source reports no benchmark figures for throughput, latency, or capacity, so the validation is described qualitatively rather than with measured results.
The players
Hewlett Packard Enterprise (HPE)
A large enterprise infrastructure company whose ProLiant servers, networking and Telco Cloud Suite supply the hardware and integration layer for this deployment model.
Ericsson
A Swedish telecommunications equipment maker whose dual-mode 5G Core network functions are the core software being validated on the stack.
Red Hat
An open-source software company owned by IBM whose OpenShift Kubernetes platform hosts the containerized 5G Core workloads.
The details
The 5G Core network functions run as containerized workloads on Red Hat OpenShift, a version of Kubernetes, the open-source system that schedules and manages containers across servers. HPE's Telco Cloud Suite framework was used to architect the design, and infrastructure-as-code, a method of defining servers and networks in machine-readable configuration files, supports consistent setup across multiple sites. Intent-based networking, where operators state a desired outcome and the system configures devices to match, is used to keep deployments consistent, and joint engineering was used to find interoperability problems before customer rollouts.
Timeline
October 2025: HPE and Ericsson announced their joint validation collaboration.
November 3, 2026: The validated deployment model release was published.
The Tech Race
The release places HPE, Red Hat and Ericsson in a race to offer pre-validated cloud-native 5G Core stacks that service providers can deploy without building their own integration. It is a vendor-led validation effort, and the source names no competing stack against which its approach is measured.
Service providers building 5G Core networks are the parties most directly affected, since the model is aimed at cutting the time between infrastructure design and an operational core. The source gives no availability date or pricing, so timing for adoption is unannounced.
The takeaway
The trajectory is toward telecom cores that ship as validated, pre-integrated stacks rather than custom projects. Watch for named service-provider deployments of this model and for any published measurement of deployment-time reduction, since the source offers none yet.
Further reading
For background on the facilities that run this kind of cloud infrastructure, see the Data Centers section.
Source note: This article includes information reported by Thefastmode.
