Skip to content

Code Vs. Data: Optimizing NFV Orchestration with Nephio - Tal Liron, Google#

ONE Summit 2024 digest Program Adjacent pick 29 April – 1 May 2024

Abstract Recording

Tal Liron, Staff Engineer, Google (Telecom Network Automation team)

Play the recording: Code Vs. Data: Optimizing NFV Orchestration with Nephio - Tal Liron, Google

  • Why: The "configuration-as-data vs. Helm charts" question is a live architectural debate for anyone running Kubernetes at scale — this makes the tradeoffs concrete using Nephio's KRM-based approach.
  • What: An argument for placing code next to the data it processes, comparing management vs. workload clusters, walking through Nephio's specialization pipeline and the operator reconciliation loop, and contrasting Nephio's configuration-as-data (CaD) paradigm with Helm charts — "breaking the Helm chart apart and putting the pieces where they belong." (from abstract only)
  • How: KRM resources as the data model, with the specialization pipeline transforming generic blueprints into environment-specific packages and reconciliation loops maintaining state continuously.
  • Where applicable: Kubernetes orchestration design generally; the CaD-vs-Helm analysis applies beyond telco. Telco-flavored context, but the architectural argument is general.