Multus configuration
To use Multus, you must create network attachment definitions (NADs) before deploying the Fusion Data Foundation cluster, which is later attached to the cluster. For more information, see Creating network attachment definitions.
To attach additional network interfaces to a pod, you must create configurations that define how
the interfaces are attached. You specify each interface by using a
NetworkAttachmentDefinition custom resource (CR). A Container Network Interface
(CNI) configuration inside each of these CRs defines how that interface is created.
Fusion Data Foundation supports two types of drivers. The following tables describes the drivers and their features:
macvlan (recommended) |
ipvlan
|
| Each connection gets a sub-interface of the parent interface with its own MAC address and is isolated from the host network. | Each connection gets its own IP address and shares the same MAC address. |
Uses less CPU and provides better throughput than Linux bridge or
ipvlan. |
L2 mode is analogous to macvlan
bridge mode. |
| Almost always require bridge mode. | L3 mode is analogous to a router existing on the
parent interface. L3 is useful for Border Gateway Protocol (BGP), otherwise use
macvlan for reduced CPU and better throughput. |
| Near-host performance when network interface card (NIC) supports virtual ports/virtual local area networks (VLANs) in hardware. | If NIC does not support VLANs in hardware, performance might be
better than macvlan. |
Fusion Data Foundation supports the following two types IP address management:
whereabouts
|
DHCP |
Uses OpenShift/Kubernetes leases to select unique
IP addresses per Pod. |
Does not require range field. |
| Does not require a DHCP server to provide IPs for Pods. | Network DHCP server can give out the same range to Multus Pods as well as any other hosts on the same network. |
CAUTION:
If there is a DHCP server, ensure Multus configured IPAM does not give out the
same range so that multiple MAC addresses on the network cannot have the same IP.