Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

Spiderpool

spidernet-io.github.io

  • Free plan
  • Linux
  • API
  • Self-hosted

What Spiderpool is

Spiderpool is an open-source networking solution for Kubernetes environments running on bare metal, virtual machines, or public clouds. Its IP address management is based on custom resources and handles dual-stack networks, shared or exclusive address pools, and static addresses for stateful applications. It works with Macvlan, IPvlan, and SR-IOV, and its IPAM can pair with compatible CNI plugins such as Calico and Weave. Pods can use several underlay interfaces or combine underlay and overlay networking, with policy routing coordinated across interfaces. Documented capabilities include Pod-to-host connectivity, conflict detection for IP addresses, gateway reachability checks, and service access via kube-proxy or an eBPF-based replacement. Spiderpool also provides RDMA with RoCE and InfiniBand, assigning devices to Pods in shared or exclusive mode. The project lists storage, middleware, observability, AI training, and latency-sensitive workloads among its uses. It is free under Apache License 2.0 and describes itself as a CNCF sandbox project. Node architectures include x86-64 and arm64; SpiderSubnet requires Kubernetes v1.21 or later.

Who it suits

Spiderpool is for teams operating Kubernetes workloads that need underlay networking, RDMA, multiple interfaces, or separate network bandwidth. Its listed use cases include storage, middleware, observability, and AI training.

Good to know, and what to watch

  • Supports dual-stack IP address management
  • Works with Macvlan, IPvlan, and SR-IOV
  • Offers RoCE and InfiniBand RDMA
  • Supports x86-64 and arm64 nodes
  • Apache License 2.0
  • IPAM and multiple-NIC routing coordination are beta
  • RDMA and multi-cluster networking are alpha for listed CNIs
  • SpiderSubnet requires Kubernetes v1.21 or later

Free (Apache License 2.0)

Free

Open source

Getting started

  1. Open the Spiderpool project website
  2. Prepare Kubernetes nodes on x86-64 or arm64
  3. Deploy Spiderpool on bare metal, virtual machines, or a public cloud
  4. Select Macvlan, IPvlan, or SR-IOV networking
  5. Configure CRD-based IP address pools and interfaces
  6. Use SpiderSubnet only with Kubernetes 1.21 or later

Limits to check

The roadmap marks IPAM and multiple-NIC and routing coordination as beta. RDMA and multi-cluster networking are alpha for Macvlan, IPvlan, and SR-IOV; SpiderSubnet requires Kubernetes 1.21 or later.

The verdict

Spiderpool provides Kubernetes networking options for varied interfaces and RDMA workloads, with broad documented connectivity functions. Check the stated feature maturity and SpiderSubnet version requirement against your deployment needs.

Questions people ask

How much does Spiderpool cost?

Spiderpool is free and open source under the Apache License 2.0.

Which environments does Spiderpool support?

It supports Kubernetes on bare metal, virtual machines, and public clouds, with x86-64 and arm64 nodes.

Which CNI plugins work with Spiderpool?

Spiderpool works with Macvlan, IPvlan, and SR-IOV. Its IPAM can also work with compatible CNIs such as Calico and Weave.

Does Spiderpool support RDMA?

Yes. It supports RoCE and InfiniBand, with devices available to Pods in shared or exclusive mode.

What networking features are included?

Features include dual-stack IPAM, static addresses, multiple interfaces, policy routing, conflict detection, gateway checks, and service access through kube-proxy or an eBPF replacement.

What is required for SpiderSubnet?

SpiderSubnet requires Kubernetes version 1.21 or later.

What the maker publishes

CNI support
Spiderpool works with Macvlan, IPvlan, and SR-IOV, and its IPAM can also be used with compatible CNIs such as Calico and Weave. source
Connectivity
The project documents Pod-to-host connectivity, IP conflict detection, gateway reachability checks, and service access through kube-proxy or an eBPF-based replacement. source
Deployment requirements
Documented node architectures are x86-64 and arm64; the SpiderSubnet feature requires Kubernetes v1.21 or later. source
Feature maturity
The roadmap marks IPAM and multiple NIC and routing coordination as beta, while RDMA and multi-cluster networking are alpha for macvlan, ipvlan, and SR-IOV. source
IP address management
Its CRD-based IPAM supports dual-stack networking, shared and exclusive pools, and static IP addresses for stateful applications. source
Multiple interfaces
Pods can use multiple underlay interfaces or a combination of underlay and overlay interfaces, with policy routing managed across interfaces. source
Project status
The project describes itself as a Cloud Native Computing Foundation sandbox project. source
Purpose
Spiderpool is an underlay and RDMA networking solution for Kubernetes on bare metal, virtual machines, and public clouds. source
RDMA
Spiderpool supports RDMA using RoCE and InfiniBand, with devices available to Pods in shared or exclusive mode. source
Security and license
Spiderpool is licensed under Apache License 2.0. source
Support
The project lists CNCF Slack, a monthly community meeting, maintainer email, and a WeChat group as community contact options. source
Use cases
The project identifies storage, middleware, observability, AI training, latency-sensitive workloads, and applications needing separate network bandwidth as use cases. source

Checked against the maker's pages on 4 Oct 2026.