Kube-OVN vs Network Service Mesh

Kube-OVN combines OVN and Open vSwitch with Kubernetes for cloud-native network orchestration. Its documented features include subnet management, static IP allocation, gateways, hybrid underlay and overlay networks, VPC features, QoS, ACLs, and traffic mirroring. VPC networks provide tenants with separate address spaces and networking resources. The project recommends it for Kubernetes environments needing KubeVirt support or multi-tenant networking; KubeVirt virtual machines can live-migrate without network interruption. Documented integrations include Cilium, MetalLB, OpenStack, Submariner, and OVN interconnect. With Cilium chaining, Kube-OVN network abstractions can be used with Cilium eBPF monitoring and security capabilities. The project runs on x86_64 and arm64, and its documentation provides one-click installation scripts. It is free under Apache-2.0, deployed on-premises, and uses a centralized control plane. The project advises against it for OpenShift, public-cloud managed Kubernetes, and cases requiring an all-in-one CNI, ingress, service mesh, and observability stack.

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.