Swisscom is revising its GitOps approach for its 5G core
22 May 2024 | Research
Case study | PPTX and PDF (5 slides) | Cloud and AI Infrastructure
"Cloud-native network functions (CNFs) cannot be treated in the same way as other cloud-native applications as they must be configured via the Network Configuration Protocol (NETCONF) interface."
Swisscom already employs GitOps for the deployment and lifecycle management of its 5G core but realised that its existing approach to GitOps failed to fully adhere to the GitOps principle of continuous reconciliation. Swisscom is experimenting with how the Kubernetes Resource Model (KRM) can be used to improve the ways in which GitOps is applied to network function (NF) configuration.
Information included in this report
- An outline of the issues with Swisscom’s existing approach to GitOps
- An overview of how Swisscom plans to approach GitOps for its 5G core
- A discussion of the advantages of Swisscom’s strategy, as well as areas for potential improvement
Author
Joseph Attwood
AnalystRelated items
Case studies report
GPU-as-a-service (GPUaaS): telecoms operator case studies and analysis
Article
Should operators embrace cloud-native automation or evolve NFV MANO for autonomous networks?
Strategy report
Cloud-native automation and ETSI NFV MANO: evolution, migration and co-existence strategies