The Accidental Platform Team: Kubernetes Operators at Swisscom#

Fabian Schulz - Swisscom (with Lea Brühwiler)

• Why: The organizational counterpart to the SDC and gNMIc talks: what happens when Kubernetes operators for network automation (IPAM, inventory, NETCONF router config — the same Swisscom stack) get adopted beyond their original 5G-core scope and become "Operators as a Service" for a platform team running Kubernetes-as-a-Service.
• What: An adoption story, not an architecture story. The honest middle section is the value: a wall of real user objections ("I don't understand Kubernetes", "we were faster the old way", "there will always be manual changes on the box", "I just did it myself with a Gitlab pipeline, it's easier") and the incremental answers that overcame them.
• How: Gradual adoption (pick one easy use case, ship a prototype early, iterate on feedback), then four countermeasures: a graphical UI for people who won't use kubectl; observability and traceability (commit history, provenance of every change) to answer "how do I know where this change came from"; knowledge-sharing initiatives and regular check-ins to build trust. The before/after numbers are striking: 5G-core network provisioning dropped from multi-week sequences (change requests 5–10 days, IP tables 2 days, integration 5–10 days) to minutes-to-hours of intent creation with continuous automated testing. Reference architecture published at architecture.cncf.io.
• Where applicable: Teams building internal platform/operator tooling — the human-side lessons are the transferable part and generalize well beyond telco. Scale numbers are Swisscom-specific.