Calico Enterprise vs Network Service Mesh

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.

Network Service Mesh connects workloads across clusters and clouds through a hybrid, multi-cloud IP service mesh. Each workload can connect independently to zero or more Network Services, regardless of where it runs. The project says it works with an existing CNI without requiring changes to Kubernetes or workloads. Services can provide connectivity, security, and observability at Layer 3 and above, carrying IP or Ethernet payloads.

Clients may be Kubernetes pods, virtual machines, or physical servers. They authenticate independently, currently using SPIFFE IDs, and need authorization to attach. Clients request and close virtual wires over gRPC and can monitor connection status through a streaming call. Endpoint selection offers composition, selective composition, topology awareness, and scale from zero. A service may also provide domain-scoped DNS for connected pods. The architecture describes integration with Istio, Linkerd, Consul, and Kuma. Network Service Mesh is a CNCF sandbox project and is free and open source. Its run guide lists Docker, Go, a Kubernetes cluster, and kubectl as prerequisites; most examples require at least two worker nodes.