The landscape of network operations is undergoing a seismic shift, moving away from the traditional, manual command-line interface (CLI) approaches of the past toward a future defined by automation, programmability, and cloud-native principles. At the heart of this transformation is the integration of Kubernetes and GitOps into the networking stack—a transition that promises to bring the agility of software development to the traditionally rigid world of hardware infrastructure. In a recent and deeply technical exchange, Eric Chou sat down with Mauricio Rojas, a Principal DevOps Consulting Engineer at Nokia, to explore how these technologies are converging to redefine modern network management.
The conversation centered on the practical application of these tools, specifically focusing on Rojas’s pioneering work with the NetOpsKube project. As networks become increasingly complex, the industry is looking toward open-source tooling and standardized orchestration to manage everything from core aggregation to the edge. The dialogue provided a comprehensive look at how the principles that revolutionized the data center are now being applied to the very backbone of the internet, including Broadband Network Gateways (BNGs) and core routing infrastructure.
The Evolution of NetOps: From Manual Configuration to Kubernetes Orchestration
For decades, network engineering was a discipline of individual expertise and manual intervention. Engineers would log into devices one by one, applying configurations that were often documented only in static text files or spreadsheets. However, as the scale of global networks has exploded, these traditional methods have become unsustainable. Mauricio Rojas, through his role at Nokia and his contributions to the networking community, has been at the forefront of advocating for a "NetOps" approach that mirrors the DevOps movement in software engineering.
The core of this shift is Kubernetes. While originally designed for container orchestration in the application layer, Kubernetes has proven to be a remarkably flexible platform for managing almost any declarative state. In the context of networking, Kubernetes serves as the control plane that ensures the actual state of the network matches the desired state defined by the engineers. This move toward a "controller-based" architecture is a departure from the "script-based" automation of the early 2010s, providing a more robust and self-healing framework for infrastructure management.
Rojas’s project, NetOpsKube, represents a tangible manifestation of this philosophy. By leveraging a stack of Kubernetes, GitOps workflows, and specialized open-source tools, NetOpsKube provides a blueprint for core and aggregation operators to manage their networks at any scale. The project aims to democratize high-end automation, making it accessible not just to hyperscalers with massive engineering teams, but also to smaller regional providers and enterprise operators who need reliable, repeatable, and transparent network management.
NetOpsKube and the Role of GitOps in Modern Infrastructure
A significant portion of the discussion focused on the mechanics of GitOps and its necessity in modern networking. GitOps is a methodology where the entire configuration of the infrastructure is stored in a version-controlled repository, typically Git. This repository serves as the single source of truth. When a change is needed, an engineer submits a pull request; once reviewed and merged, an automated system—often a Kubernetes operator—synchronizes those changes with the physical or virtual network devices.
This approach brings several immediate benefits to network reliability. First, it provides a complete audit trail of every change made to the network, including who made the change and why. Second, it allows for rapid rollbacks in the event of an error. If a configuration update causes an outage, reverting to the previous known-good state is as simple as reverting a commit in Git.
