5c7e7c0913
For IP allocation schemes that cannot be interface agnostic, the ipvlan plugin can be chained with an earlier plugin that handles this logic. If "master" is omitted from the ipvlan configuration, then the previous Result must contain a single interface name for the ipvlan plugin to enslave. If "ipam" is omitted, then the previous Result is used to configure the ipvlan interface.
plugins
Some CNI network plugins, maintained by the containernetworking team. For more information, see the individual READMEs.
Plugins supplied:
Main: interface-creating
bridge: Creates a bridge, adds the host and the container to it.ipvlan: Adds an ipvlan interface in the containerloopback: Creates a loopback interfacemacvlan: Creates a new MAC address, forwards all traffic to that to the containerptp: Creates a veth pair.vlan: Allocates a vlan device.
IPAM: IP address allocation
dhcp: Runs a daemon on the host to make DHCP requests on behalf of the containerhost-local: maintains a local database of allocated IPs
Meta: other plugins
flannel: generates an interface corresponding to a flannel config filetuning: Tweaks sysctl parameters of an existing interfaceportmap: An iptables-based portmapping plugin. Maps ports from the host's address space to the container.
Sample
The sample plugin provides an example for building your own plugin.