kube-network-policies vs Multus CNI
kube-network-policies
kube-network-policies.sigs.k8s.ioMultus CNI
github.comSide by side
| Figure | kube-network-policies | Multus CNI |
|---|---|---|
| Price from | Free | — |
| Free plan | Yes | — |
| Free trial | — | — |
| Open source | — | — |
| Linux | Yes | Yes |
| API | — | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 0 |
| Spec score · Container Networking Software | 8.1 (#4) | 7.0 (#21) |
| Integrations | ANP and BANP support integrates with the Kubernetes Network Policy API custom resource definitions. | The project gives VLAN, VXLAN and PTP as examples of networks reached through other CNI plugins. |
| License | The repository lists the Apache-2.0 license. | The repository lists the Apache-2.0 license. |
| Purpose | A userspace implementation that enforces Kubernetes network policies by intercepting packets with Linux NFQUEUE. | Multus CNI is a Kubernetes CNI meta-plugin that attaches multiple network interfaces to pods by calling other CNI plugins. |
| Support | The repository README lists the Kubernetes Slack #sig-network channel and the sig-network mailing list for maintainers and community support. | The project directs users to open a GitHub issue or ask questions in the Network Plumbing Working Group Slack #general channel. |
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.