CableLabs Snaps Kubernetes Into Its NFV, SDN Platform Stack

CableLabs added Kubernetes support to an overarching program to facilitate the adoption of SDN and NFV within the CableLabs’ community. Those efforts are based on its SDN/NFV Application development Platform and Stack (SNAPS) initiative. Randy Levensalor, lead architect for wired technologies at CableLabs, wrote in a blog post that the SNAPS-Kubernetes platform provides easy-to-install infrastructure software for lab and development projects. It helps to deliver virtual network functions (VNFs) that use fewer resources, are more fault-tolerant, and can more quickly scale to meet demand. It was developed with consulting firm Aricent, which was part of the initial SNAPS development. Levensalor explained that the Kubernetes support was part of the second wave of NFV maturity that the company has labeled as “cloud native.” This is targeted at edge and remote locations where compute resources are limited by space and power availability. “Containers and Kubernetes excel in this quickly evolving section of the market,” Levensalor wrote. “These solutions aren’t yet as mature as OpenStack and other virtualization solutions, but they are lighter weight and integrate software and infrastructure management. This means that Kubernetes will scale and fail over applications, and the software updates are also managed.” CableLabs’ first wave of NFV maturity was “lift and shift,” which involved the deployment of virtual machines (VMs) running in an OpenStack environment. The third wave is around autonomous networks, which is not expected to hit the market for several years. The Kubernetes platform is based on the container orchestrator’s 1.10 release, which was unveiled at the end of March. The Kubernetes Project released a 1.11 version at the end of June. Levensalor said that CableLabs will update to the latest Kubernetes version as “new releases stabilize and we have time to validate these releases.” SNAPS-Kubernetes will initially limit support to Docker-based containers because Docker is the most widely used container platform. Levensalor noted that it could add support for other container models that prove to be more suited for specific use cases.