readystack/flannel repository overview

⁠flannel

readystack/flannel:v0.28.10-CE-ubuntu24.04-r1

Source, recipe and records

• Source and build recipe: https://readystack.dev/products/flannel/recipe⁠
• Upstream source at this release's pinned commit (v0.28.10): https://github.com/flannel-io/flannel/tree/0f70536f15f281279dab39fb9d575c646c7eea34⁠
• Product page: https://readystack.dev/products/flannel⁠
• Hermetic Build Kit for this release (free with an account): https://readystack.dev/products/flannel⁠
• Release history (JSON): https://readystack.dev/api/releases/flannel⁠
• Defect record: https://readystack.dev/defects.html?product=flannel⁠
• Today's scan: https://readystack.dev/products/flannel#pp-grade⁠
• Report an issue: https://github.com/ReadyStackFree/readystack/issues/new?template=bug.yml&product=flannel⁠
• Signing key (cosign): https://readystack.dev/keys/cosign.pub⁠
• Part of the Kubernetes VM Stack: https://readystack.dev/stacks/kubernetes-vm-stack⁠

A cosign-signed build of https://github.com/flannel-io/flannel⁠ v0.28.10 (Apache-2.0), commit 0f70536f15f281279dab39fb9d575c646c7eea34; iptables-wrapper from https://github.com/kubernetes-sigs/iptables-wrappers⁠ (Apache-2.0) at bfef9e5087a198b50a4124bb9ce9d2c7c99025dd, built clean-room from official upstream source by ReadyStack⁠.

⁠Who uses it and why

Who: Kubernetes cluster operators who need a simple network that connects pods across nodes.

Why: flannel makes every pod's address reachable across the cluster. An agent on each host leases that host a subnet from a shared range and carries traffic between hosts, for example over VXLAN.

Use case: A team building an on-premises Kubernetes cluster needs pods on different nodes to reach each other without port mapping. flannel runs on every node, gives each node a subnet of the pod address range, and forwards pod traffic between nodes over VXLAN.

About the upstream project, written from its own description: https://github.com/flannel-io/flannel⁠

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:18ed7f68631367725ac49bc573bb3b804e997469a7a8a04958a1a74b6cfe33ce on 2026-10-29.

• Scan scores — we scan every image we publish every day (an SBOM made with syft, vulnerabilities matched with grype, scored with cerodeo-v1, the rubric ce.rodeo published until 2026-10-26) and record each scan with how its score was derived. This release's first and latest scan: https://readystack.dev/products/flannel⁠
• ReadyStack release check — passed at release on 2026-10-29: no fixable critical or high vulnerability (Docker Scout and OSV), a non-root user, SBOM and provenance attached. This is ReadyStack's own test, not a Docker grade; vulnerabilities published since then are in today's result at https://readystack.dev/queue⁠.
• Signed — cosign signature by the ReadyStack release key (fingerprint 04daa92344a52dbc) on this release's index digest sha256:18ed7f68631367725ac49bc573bb3b804e997469a7a8a04958a1a74b6cfe33ce; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/flannel:v0.28.10-CE-ubuntu24.04-r1.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (flannel).
• Built from source by ReadyStack.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is v0.28.10-CE-ubuntu24.04-r1 — the release listed at readystack.dev. Release tags use the pattern <upstream-version>-CE-<base-os>-r<N>; the current one is signed, attested (SBOM + provenance), and is provided under the ReadyStack Agreement⁠.

• Earlier release tags (an older version or revision in the same pattern) are superseded. They stay pullable so existing deployments can pin them, but they are no longer re-graded, and fixes appear only in newer releases: move to the current release. For a superseded release's build kit, ask support.

• Release tags never move, so pulling the same tag again never changes the image. To be offered each new release automatically (a new revision r<N+1>, or a new upstream version), use the ReadyStack Renovate preset: https://readystack.dev/updates.html⁠

• Any tag beginning with internal- is an engineering-pipeline artifact published for build observability. It is unsupported, may change or disappear without notice, and must not be used in production.

# ✓ current release
docker pull readystack/flannel:v0.28.10-CE-ubuntu24.04-r1

# ✗ unsupported (do not pull)
docker pull readystack/flannel:internal-...

This release is signed; verify it with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/flannel:v0.28.10-CE-ubuntu24.04-r1 (the signature is recorded in the public Sigstore transparency log). Support: [email protected]⁠, as set out in the ReadyStack Agreement⁠.

⁠Deployment

The kube-flannel DaemonSet (product-kits/kubevirt-stack/install/network/kube-flannel.yml, upstream's Documentation/kube-flannel.yml with our images and the cluster's pod CIDR): init containers install-cni-plugin (readystack/flannelcniplugin) and install-cni (this image, /opt/bin/install-conf), then flanneld --ip-masq --kube-subnet-mgr --healthz-port=8081 on the host network. The image's default user is the unprivileged flannel (uid 999); the pod sets runAsUser: 0 with NET_ADMIN and NET_RAW, because flanneld creates the VXLAN device, routes and iptables rules and writes /run/flannel on the host.

docker run --rm readystack/flannel:v0.28.10-CE-ubuntu24.04-r1 --version

Prints v0.28.10. flanneld itself runs as the DaemonSet.

⁠The full ReadyStack Hermetic Build Kit

The complete --network=none build kit for this image — plus admin/DB/API handbooks, the build's validation records, and its build provenance records — is a free download for any registered account at readystack.dev/products/flannel⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:6d3fb1140502d71df92ae2b107532acaf809aa42a94e2e6b9eec291fab4b8856 on 2026-10-29.

— ReadyStack · readystack.dev