November 22, 2026

Bridging the Gap Between Cloud-Native and Core Networking: Mauricio Rojas on NetOpsKube and the GitOps Revolution

In the NetOpsKube ecosystem, this is made possible through tools like the gNMIc Kubernetes Operator. The gRPC Network Management Interface (gNMI) is a protocol developed by Google and now widely supported by major vendors like Nokia, Arista, and Cisco. It allows for the streaming of telemetry and the pushing of configurations in a structured, model-driven format. By wrapping this capability in a Kubernetes operator, Rojas has enabled a system where Kubernetes can "watch" the network configuration and automatically correct any "drift"—the phenomenon where the actual state of a device deviates from the intended configuration due to manual intervention or hardware resets.

Transforming the Edge: BNGs and Subscriber Management

One of the more specialized areas Rojas and Chou explored was the application of these cloud-native principles to Broadband Network Gateways (BNGs). The BNG is a critical component in service provider networks, acting as the point where individual subscribers connect to the provider’s backbone. It handles essential functions such as authentication, authorization, and accounting (AAA), as well as traffic shaping and policy enforcement.

Historically, BNGs have been some of the most complex and difficult-to-automate components of a network because they deal with dynamic subscriber sessions rather than just static routing tables. Rojas discussed how the move toward Disaggregated BNGs (DBNG) and the use of the Control and User Plane Separation (CUPS) architecture allows for more granular management. By applying a NetOps stack to these environments, operators can manage subscriber policies and gateway configurations with the same level of automation used for web servers.

This level of automation is particularly relevant as operators look to scale their broadband offerings. The ability to deploy new BNG instances or update subscriber policies across a wide geographic area without manual intervention is a significant competitive advantage. It reduces the time-to-market for new services and minimizes the risk of human error in high-stakes environments.

The Intersection of AI, LLMs, and Network Operations

The conversation naturally pivoted to the most discussed technology of the current era: Artificial Intelligence. Specifically, Rojas and Chou examined the role of Large Language Models (LLMs) and the emerging Model Context Protocol (MCP) in the future of network operations.

While AI has been used in networking for years—primarily for anomaly detection and predictive maintenance—the rise of LLMs introduces a new interface for network management. Rojas noted that LLMs can assist engineers in generating complex configurations, interpreting dense technical documentation, and even suggesting troubleshooting steps based on telemetry data. However, the challenge remains in ensuring that these models have the correct context and that their outputs are safe to implement on live production networks.

This is where the Model Context Protocol (MCP) becomes vital. MCP is designed to provide a standardized way for AI models to interact with external data sources and tools. In a networking context, this could allow an LLM to safely query the current state of a router or check the Git repository for recent changes before suggesting a fix. By grounding the AI in the actual state of the network, operators can mitigate the risk of "hallucinations" and ensure that the AI’s suggestions are technically sound and compliant with organizational policies.