flannel-io /flannel

flannel is a network fabric for containers, designed for Kubernetes

★ 9,567⑂ 2,876👁 210⑃ 1,427● 1,190▤ 96
GoApache-2.0Created 2014-07-10
Download: v0.28.10v0.28.10 ↓0.28.102026-10-08
+0
Daily
9,567
stars
2,876
forks
210
watchers
1,427
prs
1,190
issues
96
releases

README

flannel

!flannel Logo

!Build Status


Flannel is a simple and easy way to configure a layer 3 network fabric designed for Kubernetes.

 How it works

Flannel runs a small, single binary agent called flanneld on each host, and is responsible for allocating a subnet lease to each host out of a larger, preconfigured address space.
Flannel uses either the Kubernetes API or [etcd][etcd] directly to store the network configuration, the allocated subnets, and any auxiliary data (such as the host's public IP).
Packets are forwarded using one of several [backend mechanisms][backends] including VXLAN and various cloud integrations.

 Networking details

Platforms like Kubernetes assume that each container (pod) has a unique, routable IP inside the cluster.
The advantage of this model is that it removes the port mapping complexities that come from sharing a single host IP.

Flannel is responsible for providing a layer 3 IPv4 network between multiple nodes in a cluster. Flannel does not control how containers are networked to the host, only how the traffic is transported between hosts. However, flannel does provide a CNI plugin for Kubernetes and a guidance on integrating with Docker.

Flannel is focused on networking. While the flanneld binary does not natively enforce Network Policies, the Flannel project provides ways to add policy support to your cluster.

 Network Policy

For Network Policy enforcement, options include:

 Integrated controller: The Flannel Helm chart has a netpol.enabled option that deploys the Kubernetes SIGs network policy controller alongside Flannel.
 Third-party controllers: Use Flannel for connectivity and another project for policy, for example Calico or CNI chaining with Cilium.

See Documentation/netpol.md for configuration details.

 Getting started on Kubernetes

The easiest way to deploy flannel with Kubernetes is to use one of several deployment tools and distributions that network clusters with flannel by default. For example, [K3s][k3s] sets up flannel in the Kubernetes clusters it creates using the open source [K3s Installer][k3s-installer] to drive the setup process.

Though not required, it's recommended that flannel uses the Kubernetes API as its backing store which avoids the need to deploy a discrete etcd cluster for flannel. This flannel mode is known as the kube subnet manager.

 Deploying flannel manually

Flannel can be added to any existing Kubernetes cluster though it's simplest to add flannel before any pods using the pod network have been started.

For Kubernetes v1.17+

 Deploying Flannel with kubectl

bash
kubectl apply -f https://github.com/flannel-io/flannel/releases/latest/download/kube-flannel.yml


Prefer the manifest attached to a release (or latest as above). The copy under
Documentation/kube-flannel.yml on the default branch can lag or get ahead of the
published container tags, so applying it directly may fail with missing binaries
in the image (for example install-conf).

If you use custom podCI

Top issues

Discussions

Latest release

v0.28.10 v0.28.10 2026-10-08
What's Changed
 Migrate kind e2e tests from bash_unit to Ginkgo by @thomasferrandiz in https://github.com/flannel-io/flannel/pull/2513
 build(deps): bump actions/attest-build-provenance from 4.1.1 to 4.2.2 by @dependabot[bot] in https://github.com/flannel-io/flannel/pull/2533
 build(deps): bump github/codeql-action/upload-sarif from 4.37.3 to 4.37.6 by @dependabot[bot] in https://github.com/flannel-io/flannel/pull/2532
 Migrate remaining bash_unit tests to Ginkgo / Go by @thomasferrandiz in https://github.com/flannel-io/flannel/pull/2534
 build(deps): bump k8s dependencies to v0.34.10 by 

Snapshot: 2026-11-16T09:23:14Z · Data license Apache-2.0 · JSON