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

Flannel

github.com

  • Free plan
  • Windows
  • Linux
  • Self-hosted
7.2 Club score Visit github.com

What Flannel is

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

Who it suits

Flannel suits teams deploying container networking in Kubernetes environments that can manage a privileged daemonset and choose a backend. It may also fit documented Docker deployments on Linux or Windows.

Good to know, and what to watch

  • Free and open source under Apache 2.0
  • Stores network configuration in Kubernetes API or etcd
  • WireGuard backend encrypts packets
  • Documented for Kubernetes and Docker
  • Does not enforce network policies natively
  • Only the latest release receives security fixes
  • Backend selection should not change at runtime
  • Runs privileged with host-network access

Flannel

Free

Free plan

The verdict

Flannel provides host subnets and packet forwarding for container networks, with several backend options and a recommended VXLAN choice. Teams need to plan policy enforcement separately and keep the deployment updated, since older releases do not receive security fixes.

What the maker publishes

Backends
Documented backends include VXLAN, host-gw, WireGuard, and UDP; VXLAN is the recommended choice. source
Compatibility constraint
The backend documentation says a selected backend should not be changed at runtime. source
Datastores
Flannel can store network configuration and subnet allocations in the Kubernetes API or directly in etcd. source
Deployment security
Flannel runs as a privileged daemonset with access to the host network, and its security policy advises following least privilege and keeping it updated. source
Encryption
The WireGuard backend encapsulates and encrypts packets using the in-kernel WireGuard implementation. source
How it works
A small flanneld agent on each host allocates that host a subnet lease from a configured address space. source
Integrations
The project lists kube-network-policies, Canal, K3s, and RKE2 as projects that integrate with Flannel. source
Network policy
Flannel does not natively enforce network policies, but its Helm chart can deploy a Kubernetes SIGs network policy controller alongside it. source
Notable limitation
The project maintains security fixes for the latest release only; older releases are not actively patched. source
Purpose
Flannel provides a layer 3 network fabric for containers designed for Kubernetes. source
Security reporting
The security policy directs vulnerability reports to GitHub private vulnerability reporting and says maintainers acknowledge reports within seven days. source
Support
The project points users to the #k3s channel in Rancher Users Slack, the #flannel-users channel in Calico Users Slack, and GitHub issues for bugs. source
Supported environments
The project documents Kubernetes and Docker deployments, with Linux and Windows build instructions. source
Traffic forwarding
Flannel forwards packets between hosts using backends including VXLAN and cloud integrations. source

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