Skip to content
SPECIFICTION
Get listed

DANM vs Flannel

DANM

github.com

Flannel

github.com

Side by side

FigureDANMFlannel
Price fromFreeFree
Free planYesYes
Free trial——
Open source——
Windows—Yes
LinuxYesYes
Self-hostedYesYes
Plans published11
Spec score · Container Networking Software7.8 (#9)7.8 (#10)
PurposeDANM is an end-to-end network management suite for Kubernetes, originally developed as Nokia’s TelCo-grade solution.Flannel provides a layer 3 network fabric for containers designed for Kubernetes.

Plans

DANM

  • DANMFree

DANM pricing →

Flannel

  • FlannelFree

Flannel pricing →

In their own words

DANM

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.

Visit github.com

Flannel

Flannel is a free network fabric for containers designed for Kubernetes. A small flanneld agent on each host allocates a subnet lease from a configured address space, then forwards packets between hosts using a selected backend. Documented choices include VXLAN, host-gw, WireGuard and UDP, with VXLAN recommended. WireGuard encapsulates and encrypts packets using the in-kernel WireGuard implementation. Network configuration and subnet allocations can be stored in the Kubernetes API or directly in etcd. The project documents Kubernetes and Docker deployments, with Linux and Windows build instructions. Flannel does not enforce network policies itself, though its Helm chart can deploy a Kubernetes SIGs network policy controller alongside it. It runs as a privileged daemonset with access to the host network, so the security policy advises least privilege and keeping it updated. Security fixes are maintained for the latest release only, and the backend documentation says not to change a selected backend at runtime.

Visit github.com