Evolving GitOps: Harnessing Kubernetes Resource Model for 5G Core
summary
Swisscom claims that shifting GitOps to a Kubernetes Resource Model enables intent-driven 5G core configs so operators check in only high-level intent while K8s assembles runtime details. The team prototypes a CRD/operator pipeline using KRM-driven GitOps, reconciled via Flux + Helm, integrating an open-source netbox operator to allocate addresses. They demonstrate dynamic MetalLB IP pool creation against ~2,000 pods and ~5,000 config parameters, both Ansible-driven and native operator versions, and show the operator flow working end-to-end.
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
35mEvolving GitOps: Harnessing Kubernetes Resource Model for 5G Core
31mAutomating Kubernetes Resource Management Over GitOps for the Telco Cloud RAN Prime Time
49mGitOps, a somewhat realistic scenario on Kubernetes with Flux
26mKeynote Session: GitOps as an Evolution of Kubernetes
46mA 5G deployment: as easy as GitOps with FluxCd
45mFrom DevOps to GitOps: Supercharging Your Kubernetes Workload Deployments
45mGitops: The Kubernetes way
33mKubernetes As A Service with GitOps