New Network Provisioning System Leveraging Kubernetes and Cloud Native Open Source
summary
A Kubernetes-based network provisioning system is implemented using Kubernetes custom controllers, FluxCD, and Cue to turn intent into typed device configs, store full device manifests in Git, and run GitOps deployments. It supports composite merging of multiple intents (Cue’s commutative/associative semantics), uses gNMI/OpenConfig or device drivers as operators, and coordinates all‑or‑nothing device transactions with a transaction controller. A demo configures two OpenConfig gNMI emulators from a single cluster (7 deployments) successfully; secrets and real‑device trials remain future work.
AI-written summary · about
chapters (14)
- 0:00Start
- 0:14Self Introduction
- 1:27Scope of this presentation
- 2:39Today's session
- 3:23Cases of the legacy approach
- 3:39Case1: API Automation
- 5:37Case1: Problems
- 9:15Case2: Problems
- 12:48Manage system declaratively using Kubernetes
- 17:22Modern CI/CD Pipeline with CUE
- 18:50Comparison to Network Provisioning System
- 24:04Design
- 36:39Requirements satisfied?
- 38:48Takeaways
related talks
01h 21mIntro + Deep Dive: Cloud Native Network Function (CNF) Testbed
26mKubenet: Harnessing Kubernetes for Network Automation
31mMayday! CNI Overboard!
31mCloud Native Network Observability: Treating Routers like Kubernetes Resources
35mDeclarative Networking in Declarative World, ver. 2025
32mPanel: Are We There Yet? Native Kubernetes Networking for Telecom Workloads
37mKubernetes and the CNI: Where We Are and What's Next - Casey Callendrello, CoreOS
35mDeep Dive: Network Service Mesh (NSM)