kube-network-policies vs Liqo
kube-network-policies
kube-network-policies.sigs.k8s.ioLiqo
liqo.ioSide by side
| Figure | kube-network-policies | Liqo |
|---|---|---|
| Price from | Free | — |
| Free plan | Yes | — |
| Free trial | — | — |
| Open source | — | — |
| Windows | — | Yes |
| macOS | — | Yes |
| Linux | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 0 |
| Spec score · Container Networking Software | 8.1 (#4) | 7.1 (#18) |
| Integrations | ANP and BANP support integrates with the Kubernetes Network Policy API custom resource definitions. | The installation guide describes using Helm 3 to install Liqo, and the CLI supports kubectl-style Kubernetes API access. |
| License | The repository lists the Apache-2.0 license. | The official site says Liqo is licensed under Apache-2.0. |
| Purpose | A userspace implementation that enforces Kubernetes network policies by intercepting packets with Linux NFQUEUE. | Liqo is an open-source project for creating dynamic Kubernetes multi-cluster topologies across on-premise, cloud, and edge infrastructures. |
| Requirements | The quick start prerequisites are Docker, KIND, and kubectl for its local development cluster instructions. | Liqo requires Linux kernel 5.10 or later and recommends at least 2 CPUs and 2 GB of RAM for the cluster. |
| Support | The repository README lists the Kubernetes Slack #sig-network channel and the sig-network mailing list for maintainers and community support. | The official site links to Liqo’s documentation, quick-start guide, and community Slack. |
Plans
In their own words
kube-network-policies
kube-network-policies is a free, open-source userspace implementation of Kubernetes network policies for Linux. It uses Linux NFQUEUE and nftables to capture and evaluate network traffic in userspace. The project supports standard Kubernetes NetworkPolicy, AdminNetworkPolicy (ANP) and BaselineAdminNetworkPolicy (BANP). It can identify packets from pods targeted by active policies and capture those selectively; enabling ANP or BANP disables that optimization and diverts all node traffic to userspace for evaluation. Its documented evaluation pipeline checks logging, Admin Network Policy, standard NetworkPolicy, Baseline Admin Network Policy, then allows traffic by default. ANP and CNP can match external domain names using an in-memory cache of DNS A and AAAA answers. Structured JSON logs aid troubleshooting, and the PolicyEvaluator plugin pipeline can take custom validation logic. Installation instructions cover raw Kubernetes manifests and Helm. The local development setup uses KIND and lists Docker, KIND and kubectl as prerequisites. ANP or BANP also require experimental Network Policy API CRDs before deployment. The project lists an Apache-2.0 license and directs users to the Kubernetes #sig-network Slack channel and mailing list for maintainers.
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.