Side by side
DANM vs Liqo
Both stand on container networking software. Which one you can start free with, which one lets you read the code, and what each costs once you pay.
Free plan LinuxSelf-hosted
DANM offers substantial network and tenant-management controls for self-managed Kubernetes clusters. Its manual deployment and stated Kubernetes compatibility should fit the operator’s environment before adoption.
Visit DANM Free plan LinuxMacSelf-hosted+1
Choose Liqo if you need free, open-source tooling to peer Kubernetes clusters and share namespace resources or workload capacity across them. Look elsewhere if your environment cannot meet its Linux kernel requirement or depends on officially supported Kubernetes releases older than the latest three major versions.
Visit LiqoThe facts
| DANM | Liqo | |
|---|---|---|
| Free plan | Yes | Yes |
| Open source | Not published | Not published |
| Runs on | Linux, Self-hosted | Linux, Mac, Self-hosted, Windows |
| Lowest paid plan | Free or on request | Not published |
| Plans published | 1 | None |
| Maker | Not published | Not published |
| Website | github.com | liqo.io |
| On container networking software | #8 of 28 | #12 of 28 |
DANM: what it does well
- Supports dynamic, static, or no IPv4 and IPv6 allocation.
- Can provision multiple network interfaces to a Pod.
- Documents integration with SR-IOV, MACVLAN, Calico, and Flannel.
- Production mode includes tenant and cluster network APIs.
- Free under the 3-Clause BSD License.
What to know first
- Requires users to create a cluster and install it manually.
- Deployment guide says there is no Docker container release.
- Guide identifies Kubernetes 1.17.x as tested.
- Earlier than Kubernetes 1.9.x is not officially supported.
Liqo: what it does well
- Free and open source under the Apache-2.0 license.
- Extends namespaces and replicates resources across clusters.
- Schedules workloads on remote clusters through virtual nodes.
- Connects pods with WireGuard VPN tunnels by default.
- Supports declarative peering and GitOps management with ArgoCD.
What to know first
- Requires Linux kernel 5.10 or later.
- Compatibility is guaranteed only for the latest three Kubernetes major releases.
- ServiceAccount tokens can propagate to remote clusters unless API-server support is disabled.