Evolving GitOps: Harnessing Kubernetes Resource Model for 5G Core
summary
Swisscom replaces checked-in low‑level configs with KRM-based intent resources, using Flux plus custom Kubernetes operators to dynamically assemble runtime state. A dev 5G core runs about 2,000 pods with 5,000 config parameters, so they build a NetBox operator and a controller that creates prefix claims and synthesizes MetalLB IP pools on demand; demos show LoadBalancer services receive IPs and cleanup happens via ownerReferences and Kubernetes garbage collection.
AI-written summary · about
chapters (9)
- 0:00Evolving GitOps for 5G core
- 4:135G core GitOps challenges
- 9:16Kubernetes Resource Model
- 12:47GitOps and KRM integration
- 17:50Dynamic IP pool with Ansible
- 24:57Dynamic IP pool with operator
- 29:54Dynamic config assembly gaps
- 30:38Key learnings and best practices
- 33:55Q&A
related talks
19mKeynote: Why Open Source SW, Cloud Native Implementation, and...
33mIntent-based holistic data center management
31mAn Open Source Telco Cloud Stack to Accelerate the Adoption of Cloud Native Operator Model
34mGitOps for the Free Cloud: Bridging Kubernetes and OpenStack with ORC
16mKeynote: Accelerating Innovation Through Open Source
34mDemystifying Platform Engineering with OSS
28mKeynote: GitOps Working Group Project Summary
38mEnabling 6G Innovation through Open Collaboration: The Role of Linux Foundation...