DANM vs Spiderpool

DANM is a free network management suite for Kubernetes, originally developed as Nokia’s TelCo-grade solution. Its CNI metaplugin can give a Pod multiple network interfaces and delegate their setup to other CNI plugins. Built-in IP address management supports dynamic, static, or no IPv4 and IPv6 allocation, with up to 8 million allocations per network object. The IPVLAN CNI provides L2 interfaces and supports routes and policy-based routes in Pod network namespaces. Documented integrations include Intel SR-IOV and MACVLAN, with delegation to Calico and Flannel. Production-grade mode provides TenantNetwork and ClusterNetwork APIs for administrators managing shared resources and tenants using assigned resources. An optional Svcwatcher extends Kubernetes Service discovery across a Pod’s interfaces. A webhook validates DANM API objects and connects tenant networks to administrator-configured physical interface profiles. Users must create a Kubernetes cluster and install DANM manually; its deployment guide says there is no Docker container release. That guide identifies Kubernetes 1.17.x as tested and says versions earlier than 1.9.x are not officially supported. DANM is licensed under the 3-Clause BSD License.

Spiderpool is a free, open-source Kubernetes networking solution for underlay networking and RDMA on bare metal, virtual machines, and public clouds. Its CRD-based IPAM handles dual-stack networks, shared or exclusive address pools, and static addresses for stateful applications. The project supports Macvlan, IPvlan, and SR-IOV, while its IPAM can pair with compatible CNIs such as Calico and Weave. Pods may use multiple underlay interfaces or combine underlay and overlay interfaces, with policy routing across them. Documented connectivity includes Pod-to-host access, conflict detection, gateway checks, and service access through kube-proxy or an eBPF replacement. RDMA works with RoCE and InfiniBand in shared or exclusive device modes. Use cases include storage, middleware, observability, AI training, latency-sensitive workloads, and separate bandwidth needs. It supports AMD64 and ARM64 nodes, with SpiderSubnet requiring Kubernetes 1.21 or later. Spiderpool is Apache 2.0 licensed and a CNCF sandbox project.