Calico Enterprise vs kube-network-policies

Calico Enterprise is a self-managed platform for network security and observability in Kubernetes clusters. It provides pod-to-pod networking within single clusters and across multiple clusters, with data-plane options including eBPF, nftables, iptables, Windows, and VPP. Cluster mesh connects clusters for pod communication and service discovery, while supporting policy enforcement and traffic visibility. Security controls include network- and application-layer policies, DNS policies, egress controls, and workload microsegmentation. It also provides workload-level IDS/IPS, a workload-focused WAF, and DDoS detection and prevention. For observability, Calico combines flow logs with Kubernetes context and offers network topology views, dashboards, alerts, and workload packet capture. Tigera lists support for PCI DSS, HIPAA, GDPR, SOC 2, NIST, CCPA, and custom compliance frameworks, along with continuous monitoring and audit-ready reports. Policy deployment can integrate with CI/CD tools such as ArgoCD and Jenkins. The product supports hybrid deployment and centralized control, with BGP, IP-in-IP, VXLAN, WireGuard, TCP, UDP, SCTP, ICMP, ICMPv6, and HTTP listed as supported protocols.

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.