liveBook · Manning

Multus CNI plugin

As explained in Google Anthos in Action

Multus CNI is a Kubernetes container network interface plugin that attaches multiple network interfaces to a pod.

Multus CNI enables a single Kubernetes Pod to connect to multiple networks. Anthos on bare metal uses it for CNFs that separate data-plane traffic from management or control-plane traffic, improve performance, or isolate flows. section 8.3.2

A Multus deployment uses three configuration layers:

  • Define each additional network with a NetworkAttachmentDefinition, selecting an additional CNI such as IPvlan, MacVLAN, Bridge, or SR-IOV. section 8.3.2

Interface layout

The default Kubernetes interface appears inside the Pod as eth0. Multus-created interfaces appear as net1, net2, and subsequent names, allowing a CNF to connect different network segments. section 8.3.2

How Google Anthos in Action covers it

How deep it goes
Explains interface architecture and three configuration steps, but does not detail runtime internals or troubleshooting.
Examples
Uses cluster YAML, an IPvlan NetworkAttachmentDefinition, Deployment annotations, and a CNF spanning different network segments.
What it assumes
Assumes Anthos on bare metal and familiarity with Kubernetes cluster, network, Pod, Deployment, and custom-resource manifests.
What you can do after
Apply it via Anthos cluster, NetworkAttachmentDefinition, and Pod or Deployment manifests to provision additional Pod interfaces.
How it connects
Connects Kubernetes Pods and Deployments with Anthos on bare metal, NetworkAttachmentDefinition resources, CNFs, and additional CNI implementations.
Cover of Google Anthos in Action
liveBookmanning.com
Read Google Anthos in Action on liveBook Get the book at manning.com

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.