| Calico |
Yes |
Designed for flexibility, high network performance, and advanced network administration; uses BGP routing as an underlay or IP-in-IP and VXLAN as an overlay; supports network policy management, access control lists (ACLs), and WireGuard for tunneling encryption[5]. |
| Weave Net |
Yes |
Creates a mesh overlay network connecting all cluster nodes; handles fault tolerance, load balancing, and name resolution via a Weave DNS server; uses IPsec for encryption and VXLAN for encapsulation and routing[5]. |
| Cilium |
Yes |
Can be used with multiple Kubernetes clusters and provides multi-CNI features; offers high-level inspection and pod-to-pod connectivity across clusters; manages packet inspection with network and application layer awareness; supports Kubernetes Network Policies through HTTP request filters[9]. |
| Azure CNI |
Yes |
Extends Azure Virtual Networks to containers[3]. |
| Multus CNI |
N/A |
Allows pods to have multiple network interfaces[3]. |
| OVN4NFV-K8S-Plugin |
N/A |
An OVN based CNI controller plugin to provide cloud native based Service function chaining (SFC), Multiple OVN overlay networking[3]. |
| Kube-OVN |
Yes |
Bases on OVN/OVS and provides advanced features like subnet, static IP, ACL, QoS, etc[3]. |
| Hybridnet |
N/A |
Designed for hybrid clouds, providing both overlay and underlay networking for containers in one or more clusters; overlay and underlay containers can run on the same node with cluster-wide bidirectional network connectivity[3]. |
| Terway |
N/A |
A collection of CNI Plugins based on Alibaba Cloud VPC/ECS network product[3]. |
| DANM |
N/A |
A CNI-compliant networking solution for TelCo workloads running on Kubernetes[3]. |
| Knitter |
N/A |
A CNI plugin supporting multiple networking for Kubernetes[3]. |
| cni-route-override |
N/A |
A meta CNI plugin that overrides route information[3]. |
| Spiderpool |
N/A |
An IP Address Management (IPAM) CNI plugin of Kubernetes for managing static IP for underlay network[3]. |
| Bridge |
No |
Creates a bridge and adds the host and the container to it[1]. |
| ipvlan |
No |
Adds an ipvlan interface in the container[1]. |
| loopback |
No |
Sets the state of loopback interface to up[1]. |
| macvlan |
No |
Creates a new MAC address and forwards all traffic to that to the container[1]. |
| ptp |
No |
Creates a veth pair[1]. |
| vlan |
No |
Allocates a VLAN device[1]. |
| host-device |
No |
Moves an already-existing device into a container[1]. |
| dummy |
No |
Creates a new Dummy device in the container[1]. |
| win-bridge |
No |
Creates a bridge and adds the host and the container to it (Windows specific)[1]. |
| win-overlay |
No |
Creates an overlay interface to the container (Windows specific)[1]. |
| dhcp |
No |
Runs a daemon on the host to make DHCP requests on behalf of the container[1]. |
| host-local |
No |
Maintains a local database of allocated IPs[1]. |
| static |
No |
Allocates a single static IPv4/IPv6 address to container, useful for debugging[1]. |
| tuning |
No |
Tweaks sysctl parameters of an existing interface[1]. |
| portmap |
No |
An iptables-based port mapping plugin; maps ports from the host’s address space to the container[1]. |
| bandwidth |
No |
Allows bandwidth-limiting through use of traffic control tbf (ingress/egress)[1]. |
| sbr |
No |
A plugin that configures source-based routing for an interface (from which it is chained)[1]. |
| firewall |
No |
A firewall plugin that uses iptables or firewalld to add rules to allow traffic to/from the container[1]. |
