Skip to content

Latest commit

 

History

History
96 lines (64 loc) · 4.11 KB

supported-cnis.md

File metadata and controls

96 lines (64 loc) · 4.11 KB
Raw

Supported CNIs

Galaxy supports any standard CNI plugin. You can use it as a CNI framework just like multus-cni.

While galaxy do has following builtin CNIs.

SDN CNI

Kubelet launches SDN CNI process according to CNI configuration.

SDN CNI process calls Galaxy daemon via unix socket with all args from Kubelet.

Veth CNI

Veth CNI is a overlay network plugin which creates a veth pair to connect host network namespace with container.

Veth CNI gets POD IPs from ipam CNI plugin.

Vlan CNI

Vlan CNI is a underlay network plugin which creates a veth pair to connect host network namespace with container and bridge/macvlan/ipvlan device to connect host veth pair with host eth device.

Vlan CNI supports configuring vlan for POD IPs.

Vlan CNI gets POD IPs either from CNI Args ipinfos=[{"ip":"192.168.0.68/26","vlan":2,"gateway":"192.168.0.65"}] or ipam CNI plugin.

This is the configuration of Vlan CNI.

type NetConf struct {
	types.NetConf
	// The device which has IDC ip address, eg. eth0 or eth0.12 (A vlan device)
	Device string `json:"device"`
	// The candidate devices if device is empty. Cni picks an available device accounding to the device order.
	Devices []string `json:"devices"`
	// Supports macvlan, bridge or pure(which avoid create unnecessary bridge), default bridge
	Switch string `json:"switch"`
	// Supports ipvlan mode l2, l3, l3s, default is l3
	IpVlanMode string `json:"ipvlan_mode"`
	// Disable creating default bridge
	DisableDefaultBridge *bool `json:"disable_default_bridge"`
	// bridge name if no vlan, default docker
	DefaultBridgeName string `json:"default_bridge_name"`
	// bridge name prefix for all bridge device, default docker
	BridgeNamePrefix string `json:"bridge_name_prefix"`
	// vlan name prefix for all vlan device, default vlan
	VlanNamePrefix string `json:"vlan_name_prefix"`
    // Send arp request
    GratuitousArpRequest bool `json:"gratuitous_arp_request"`
}

If you want to create vlan device youself, you can set device=$vlanDev, otherwise setting it to your network card name, Vlan CNI will create vlan devices.

If you want to use ipvlan when Switch=ipvlan, you can also set ipvlan mode, option values likel2, l3, l3s, default ipvlan mode is l3.

Note: If you use ipvlan in l3 or l3s mode, you may have to set gratuitous_arp_request: true

SRIOV CNI

SRIOV CNI is a underlay network plugin which makes use of SR-IOV on Ethernet Server Adapters. It allocates a VF device and puts it into container network namespace.

You can check if your intel card supports SR-IOV via FAQ

SRIOV CNI gets POD IPs either from CNI Args ipinfos=[{"ip":"192.168.0.68/26","vlan":2,"gateway":"192.168.0.65"}] or ipam CNI plugin.

TKE route ENI CNI

TKE route ENI CNI is a Tencent cloud ENI network plugin which creates a veth pair to connect host network namespace with container and policy routing on host to connect host veth pair with ENI eth device.

TKE route ENI CNI gets POD IPs either from CNI Args ipinfos=[{"ip":"192.168.0.68/26","vlan":2,"gateway":"192.168.0.65"}] or ipam CNI plugin.

underlay-veth CNI

Underlay-veth CNI is a underlay network plugin which creates a veth pair to connect host network namespace with container.

Compare with Vlan CNI, underlay-veth cni will not create any bridge device and using host route rules for packet forwarding.

Underlay-veth CNI gets POD IPs either from CNI Args ipinfos=[{"ip":"192.168.0.68/26","vlan":2,"gateway":"192.168.0.65"}] or ipam CNI plugin.

Underlay-veth CNI supports configuring vlan for POD IPs, and support multi-vlanId in single node.

Compare with vlan CNI, underlay-veth CNI will not create vlan devices for host. The OS administrator should pre-configure vlan devices(with ip address) if needed.

This is the configuration of underlay-veth CNI.

type NetConf struct {
	types.NetConf
	// The device which has IDC ip address, eg. eth0
	Device string `json:"device"`
}