liveBook · Manning

Multi-NIC pod

As explained in Google Anthos in Action

A multi-NIC pod is a Kubernetes pod configured with multiple network interfaces.

A multi-NIC pod connects one Kubernetes pod to multiple networks. Anthos on bare metal provides this capability through a Multus CNI implementation, supporting data-plane and management-plane separation, performance, security, and network-flow isolation. Kubernetes exposes the default interface as eth0 and additional interfaces as net1, net2, and so on. section 8.3.2

Configure the capability in three stages:

  • Enable multipleNetworkInterfaces: true under the clusterNetwork section of the Anthos bare metal cluster custom resource. section 8.3.2
  • Define each additional network with a NetworkAttachmentDefinition, selecting an additional CNI such as IPvlan, MacVLAN, Bridge, or SR-IOV. section 8.3.2
  • Assign networks to pods or deployments with the k8s.v1.cni.cncf.io/networks annotation, using each attachment’s namespace and name. section 8.3.2

How Google Anthos in Action covers it

How deep it goes
Explains architecture and three configuration steps, then restricts attachments to selected node pools.
Examples
Uses cluster YAML, IPvlan attachment configuration, and deployment annotations naming two additional networks.
What it assumes
Assumes Kubernetes cluster and workload-manifest familiarity while specifying the required Anthos networking resources and annotations.
What you can do after
Operate/configure multi-network pods by enabling Anthos networking, defining attachments, and assigning them to workloads.
How it connects
Connects Kubernetes pods with Multus CNI, NetworkAttachmentDefinition resources, additional CNI plugins, and node pools.
Cover of Google Anthos in Action
liveBookmanning.com
Read Google Anthos in Action on liveBook Get the book at manning.com

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.