Evolving GitOps: Harnessing Kubernetes Resource Model for 5G Core
summary
Swisscom claims a Kubernetes Resource Model approach reduces toil for a 5G core that currently spans 2,000 pods and 5,000 interdependent configuration parameters. Demos show a working hydration pattern: an input intent renders a prefix claim (PV/PVC style) and produces a MetalLB IP pool, with a newly open‑sourced netbox operator reconciling status. Three implementations are shown—Ansible, KForm, Kubernetes operator—with Ansible/KForm lacking built‑in reconciliation while the operator reconciles immediately.
AI-written summary · about
chapters (13)
- 0:00Introduction and motivation
- 2:29Swisscom’s TechCo transformation
- 4:575G core challenges overview
- 7:03Config abstraction philosophy
- 9:55Limitations of existing tools
- 10:58NetBox operator announcement
- 13:45Demo: Ansible for config hydration
- 17:20Demo: Kform for config hydration
- 20:33Demo: Kubernetes operator approach
- 24:07Comparison of solutions
- 25:13Key takeaways and tooling gap
- 27:22Future roadmap and next steps
- 29:47Q&A session
related talks
43mEvolving GitOps: Harnessing Kubernetes Resource Model for 5G Core
31mAutomating Kubernetes Resource Management Over GitOps for the Telco Cloud RAN Prime Time
44mWhy is it so Hard to Run a 5G Core on Kubernetes—and What Needs to Change for 6G
33mKubernetes As A Service with GitOps
35mMigrating the Next Generation Mobile Core Towards 5G with Kubernetes
06mKeynote: Beyond Automation: Kubernetes Success Requires a GitOps Mindset
45mGitops: The Kubernetes way
23mJust Claim It: Simplifying Network Automation with NetBox Operator...