CNI Plugins vs Liqo
CNI Plugins
github.comLiqo
liqo.ioSide by side
| Figure | CNI Plugins | Liqo |
|---|---|---|
| Price from | Free | — |
| Free plan | Yes | — |
| Free trial | — | — |
| Open source | — | — |
| Windows | Yes | Yes |
| macOS | — | Yes |
| Linux | Yes | Yes |
| Self-hosted | — | Yes |
| Plans published | 1 | 0 |
| Spec score · Container Networking Software | 7.8 (#8) | 7.1 (#18) |
| License | The repository is distributed under the Apache License, Version 2.0. | The official site says Liqo is licensed under Apache-2.0. |
| Purpose | CNI Plugins is a collection of reference and example network plugins maintained by the containernetworking team. | Liqo is an open-source project for creating dynamic Kubernetes multi-cluster topologies across on-premise, cloud, and edge infrastructures. |
| Support | The project directs questions to the cni-dev mailing group or the #cni channel on CNCF Slack. | The official site links to Liqo’s documentation, quick-start guide, and community Slack. |
Plans
In their own words
CNI Plugins
CNI Plugins is a collection of reference and example network plugins for configuring connectivity in Linux and Windows containers. CNI supplies a specification and libraries, plus a command-line tool for executing plugins and a Go library for application integration. Interface options include bridge, ipvlan, loopback, macvlan, point-to-point, VLAN, host-device, and dummy; Windows-specific plugins include win-bridge and win-overlay. IP address management choices cover DHCP, host-local allocation tracking, and static IPv4 or IPv6 allocation. Meta plugins handle interface tuning, port mapping, bandwidth limits, source-based routing, and firewall rules, and a sample plugin illustrates custom plugin development. CNI focuses on connecting containers and removing allocated resources when a container is deleted. The project is distributed under Apache License 2.0 and is a Cloud Native Computing Foundation project. It is free, with a plan listed at free. Linux and Windows are supported; the latest release page lists Linux archives for amd64, arm, and arm64.
Liqo
Liqo connects Kubernetes clusters into multi-cluster topologies, allowing them to share namespaces, resources, and workload capacity. It can extend consumer namespaces and replicate configurations, secrets, services, and other resources. A remote cluster appears as a virtual node, so the consumer cluster can schedule workloads there. Liqo’s network fabric connects pods across peered clusters using WireGuard VPN tunnels by default, and it describes cross-cluster storage support for stateful workloads. Peering can be declared with Kubernetes resources and managed through GitOps tools such as ArgoCD. The liqoctl CLI installs and uninstalls Liqo, manages peering, configures namespace-level offloading, and reports status. Liqo targets heterogeneous on-premises, public cloud, edge, and multi-cloud environments, with support listed for Kubernetes, Kubeadm, K3s, K0s, AKS, EKS, GKE, Aruba Cloud KaaS, and OpenShift. It is free and open source under Apache-2.0. Liqo requires Linux kernel 5.10 or later and recommends at least 2 CPUs and 2 GB of RAM for a cluster.