Home > Communication Service Provider Solutions > Telecom Technical White Papers > Design and Optimize a 5G Telco Cloud > Deployment models
In the telco cloud evolution, there has been a shift in technology and deployment models to meet the requirements of 5G and the transition to containerized and cloud-native workloads. Traditionally, the telco cloud relied on a virtualization layer like OpenStack with ETSI-MANO integration. However, as the industry embraced 5G and the need for more agility, the adoption of Kubernetes on top of OpenStack emerged (Phase A). While providing flexibility, this approach also introduced additional complexity as parallel multicloud deployments of OpenStack and OpenShift on bare metal became more common.
Many telcos are in this transitional phase (Phase B), where OpenStack and OpenShift co-exist, serving different purposes. Kubernetes is increasingly used for cloud-native applications, while OpenStack continues supporting legacy workloads such as 2G and 3G. This coexistence is necessary to maintain essential services like emergency communications mandated by many countries.
The ideal scenario (Phase C) envisions a complete phasing out of OpenStack, with Kubernetes becoming the primary platform for all telco applications. However, achieving this goal is a long-term process that could take 7 to 10 years. Recognizing this trend, Red Hat has proposed an intermediate solution between Phases B and C. They suggest running OpenStack on top of OpenShift, leveraging the capabilities of Kubernetes to enhance the deployment and management of telco cloud infrastructure.
This evolving landscape reflects the industry's journey towards a fully cloud-native telco environment. The path to Phase C may take time. The convergence of OpenStack and Kubernetes on the OpenShift platform highlights the commitment to innovation and the pursuit of optimal solutions for telco cloud deployments.