liveBook · Manning

Cloud-native network function

As explained in Google Anthos in Action

A cloud-native network function (CNF) is a telecommunications network function designed to run as modular, containerized software on cloud-native infrastructure.

A cloud-native network function (CNF) is a cloud-native application that implements telecommunications network functionality. It consists of one or more microservices developed with principles such as immutable infrastructure, declarative APIs, and repeatable deployment. CNFs extend the move from physical appliances to virtualized network functions (VNFs) toward containerized workloads, with the aim of improving portability, agility, manageability, and efficiency. section 8.1.3 section 8.0

The transition is relevant to 5G network functions and the radio access network. Virtualizing mobile base stations was considered for network functions virtualization (NFV) but did not effectively materialize there; containerized workloads and new 5G radio functions are pushing these functions toward CNFs. section 8.1.2

On Anthos on bare metal, a CNF that needs separate network paths can use multiple interfaces per Pod:

  • Enable multipleNetworkInterfaces in the clusterNetwork portion of the bare-metal cluster configuration. section 8.3.2
  • Define additional networks with NetworkAttachmentDefinition resources, then assign them through Pod or deployment annotations. The default Kubernetes interface appears as eth0; additional interfaces appear as net1, net2, and so on by default. section 8.3.2
  • Choose an additional-interface CNI appropriate to the deployment: IPvlan, MacVLAN, Bridge, or SR-IOV. Separate data-plane traffic from management or control traffic when performance, security, or flow isolation requires it. section 8.3.2
Figure 8.6 CNF using multiple NICs to connect different network segments
08-06

The diagram shows a CNF using multiple NICs to connect to different network segments, making the traffic-separation requirement concrete. section 8.3.2

Deployment location and management model remain choices, not properties of the CNF itself. Google Distributed Cloud Edge supports virtualized and cloud-native network functions on Anthos on bare metal at public-cloud, telco, or enterprise edge sites. Its managed infrastructure and fleet capabilities can support distributed deployments; Anthos capabilities include multiple Pod interfaces, hardware accelerators, and large-fleet management. section 8.3.1 section 8.4

How Google Anthos in Action covers it

How deep it goes
Defines CNFs through microservices and cloud-native principles, then details multi-interface deployment on Anthos rather than implementing a network function.
Examples
Uses cluster configuration, NetworkAttachmentDefinition resources, deployment annotations, and a multi-NIC network-segment diagram.
What it assumes
Assumes familiarity with Kubernetes Pods and cluster configuration while defining CNFs and their cloud-native principles.
What you can do after
Operate/configure it on Anthos on bare metal by enabling multiple Pod interfaces and assigning defined networks to CNF Pods.
How it connects
Connects CNFs to network functions virtualization, VNFs, 5G, radio access networks, Kubernetes Pods, and Multus CNI.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Google Anthos in Action. The section links point to the parts of the book it draws on.