How secondary networks are implemented

All of the pods in the node still use the node-wide default network to maintain connectivity across the node. Every pod has an eth0 interface that is attached to the node-wide pod network.

  • You can view the interfaces for a pod by using the oc get pod <pod_name> -o=jsonpath='{ .metadata.annotations.k8s\.v1\.cni\.cncf\.io/network-status }' command.

  • If you add secondary network interfaces that use the MicroShift Multus CNI, they are named net1, net2, …​, netN.

  • The CNI configuration is created when the MicroShift Multus DaemonSet starts. This configuration is autogenerated and includes the primary CNI that is the default delegate. For MicroShift, the default CNI is OVN-Kubernetes.

← Previous: Use case: Secondary networks for network isolation | ↑ Up: Secondary networks in MicroShift | ⌂ Home: Red Hat build of MicroShift | Next: How to attach secondary networks to pods →