[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-5085":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":16,"stars7d":17,"stars30d":18,"stars90d":16,"forks30d":16,"starsTrendScore":19,"compositeScore":20,"rankGlobal":10,"rankLanguage":10,"license":21,"archived":22,"fork":22,"defaultBranch":23,"hasWiki":22,"hasPages":24,"topics":25,"createdAt":10,"pushedAt":10,"updatedAt":33,"readmeContent":34,"aiSummary":35,"trendingCount":16,"starSnapshotCount":16,"syncStatus":36,"lastSyncTime":37,"discoverSource":38},5085,"flannel","flannel-io\u002Fflannel","flannel-io","flannel is a network fabric for containers, designed for Kubernetes","",null,"Go",9473,2893,211,17,0,11,24,6,41,"Apache License 2.0",false,"master",true,[26,27,5,28,29,30,31,32],"docker","docker-image","go","kubernetes","network","overlay-network","subnet","2026-06-12 02:01:08","# flannel\n\n![flannel Logo](logos\u002Fflannel-horizontal-color.png)\n\n![Build Status](https:\u002F\u002Fgithub.com\u002Fflannel-io\u002Fflannel\u002Factions\u002Fworkflows\u002Fbuild.yaml\u002Fbadge.svg?branch=master)\n[![OpenSSF Scorecard](https:\u002F\u002Fapi.scorecard.dev\u002Fprojects\u002Fgithub.com\u002Fflannel-io\u002Fflannel\u002Fbadge)](https:\u002F\u002Fscorecard.dev\u002Fviewer\u002F?uri=github.com%2Fflannel-io%2Fflannel)\n\nFlannel is a simple and easy way to configure a layer 3 network fabric designed for Kubernetes.\n\n## How it works\n\nFlannel 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.\nFlannel 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).\nPackets are forwarded using one of several [backend mechanisms][backends] including VXLAN and various cloud integrations.\n\n### Networking details\n\nPlatforms like Kubernetes assume that each container (pod) has a unique, routable IP inside the cluster.\nThe advantage of this model is that it removes the port mapping complexities that come from sharing a single host IP.\n\nFlannel 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.\n\nFlannel is focused on networking. For network policy, other projects such as [Calico][calico] can be used.\n\n## Getting started on Kubernetes\n\nThe 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.\n\nThough 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*.\n\n### Deploying flannel manually\n\nFlannel 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.\n\nFor Kubernetes v1.17+\n\n#### Deploying Flannel with kubectl\n\n```bash\nkubectl apply -f https:\u002F\u002Fgithub.com\u002Fflannel-io\u002Fflannel\u002Freleases\u002Flatest\u002Fdownload\u002Fkube-flannel.yml\n```\n\nIf you use custom `podCIDR` (not `10.244.0.0\u002F16`) you first need to download the above manifest and modify the network to match your one.\n\n#### Deploying Flannel with Helm\n\n```bash\n# Needs manual creation of namespace to avoid Helm error\nkubectl create ns kube-flannel\nkubectl label --overwrite ns kube-flannel pod-security.kubernetes.io\u002Fenforce=privileged\n\nhelm repo add flannel https:\u002F\u002Fflannel-io.github.io\u002Fflannel\u002F\nhelm install flannel --set podCidr=\"10.244.0.0\u002F16\" --namespace kube-flannel flannel\u002Fflannel\n```\n\nSee [Kubernetes](Documentation\u002Fkubernetes.md) for more details.\n\nIn case a firewall is configured ensure to enable the right port used by the configured [backend][backends].\n\nFlannel uses `portmap` as CNI network plugin by default; when deploying Flannel ensure that the [CNI Network plugins][Network-plugins] are installed in `\u002Fopt\u002Fcni\u002Fbin` the latest binaries can be downloaded with the following commands:\n\n```bash\nARCH=$(uname -m)\n  case $ARCH in\n    armv7*) ARCH=\"arm\";;\n    aarch64) ARCH=\"arm64\";;\n    x86_64) ARCH=\"amd64\";;\n  esac\nmkdir -p \u002Fopt\u002Fcni\u002Fbin\ncurl -O -L https:\u002F\u002Fgithub.com\u002Fcontainernetworking\u002Fplugins\u002Freleases\u002Fdownload\u002Fv1.7.1\u002Fcni-plugins-linux-$ARCH-v1.7.1.tgz\ntar -C \u002Fopt\u002Fcni\u002Fbin -xzf cni-plugins-linux-$ARCH-v1.7.1.tgz\n```\n\nFlannel requires the br_netfilter module to start and from version 1.30 kubeadm doesn't check if the module is installed and Flannel will not rightly start in case the module is missing.\n\n## Getting started on Docker\n\nflannel is also widely used outside of Kubernetes. When deployed outside of Kubernetes, etcd is always used as the datastore. For more details integrating flannel with Docker see [Running](Documentation\u002Frunning.md)\n\n## Documentation\n\n- [Building (and releasing)](Documentation\u002Fbuilding.md)\n- [Configuration](Documentation\u002Fconfiguration.md)\n- [Backends](Documentation\u002Fbackends.md)\n- [Running](Documentation\u002Frunning.md)\n- [Troubleshooting](Documentation\u002Ftroubleshooting.md)\n- [Projects integrating with flannel](Documentation\u002Fintegrations.md)\n\n## Contact\n\n- Slack:\n  - #k3s on [Rancher Users Slack](https:\u002F\u002Fslack.rancher.io)\n  - #flannel-users on [Calico Users Slack](https:\u002F\u002Fslack.projectcalico.org)\n- Planning\u002FRoadmap: [ROADMAP.md][roadmap], [milestones][milestones]\n- Bugs: [issues][flannel-issues]\n\n## Community Meeting\n\nThe Flannel Maintainer Community runs a meeting on the third Thursday of each month at 8:30 AM PST (16:30 UTC). This meeting is used to discuss issues, open pull requests, and other topics related to Flannel should the need arise.\n\nThe meeting agenda and Teams link can be found here: [Flannel Community Meeting Agenda](https:\u002F\u002Fdocs.google.com\u002Fdocument\u002Fd\u002F1kPMMFDhljWL8_CUZajrfL8Q9sdntd9vvUpe-UGhX5z8)\n\n## Contributing\n\nSee [CONTRIBUTING][contributing] for details on submitting patches and the contribution workflow.\n\n## Reporting bugs & security vulnerabilities\n\nSee [reporting bugs][reporting] for details about reporting any issues.\n\nFor security issues, please first check our [security policy](SECURITY.md).\n\n## Licensing\n\nFlannel is under the Apache 2.0 license. See the [LICENSE][license] file for details.\n\n[calico]: http:\u002F\u002Fwww.projectcalico.org\n[etcd]: https:\u002F\u002Fgo.etcd.io\u002Fetcd\u002Fv3\n[contributing]: CONTRIBUTING.md\n[license]: https:\u002F\u002Fgithub.com\u002Fflannel-io\u002Fflannel\u002Fblob\u002Fmaster\u002FLICENSE\n[milestones]: https:\u002F\u002Fgithub.com\u002Fflannel-io\u002Fflannel\u002Fmilestones\n[flannel-issues]: https:\u002F\u002Fgithub.com\u002Fflannel-io\u002Fflannel\u002Fissues\n[backends]: Documentation\u002Fbackends.md\n[roadmap]: ROADMAP.md\n[reporting]: Documentation\u002Freporting_bugs.md\n[k3s-installer]: https:\u002F\u002Fgithub.com\u002Fk3s-io\u002Fk3s\u002F#quick-start---install-script\n[k3s]: https:\u002F\u002Fk3s.io\u002F\n[Network-plugins]: https:\u002F\u002Fgithub.com\u002Fcontainernetworking\u002Fplugins\n","Flannel 是一个专为 Kubernetes 设计的容器网络解决方案。其核心功能在于通过分配独立的子网给集群中的每个节点，实现跨主机的容器间通信，并支持多种后端机制如 VXLAN 和各种云集成来转发数据包。技术上，Flannel 使用 Go 语言编写，支持通过 Kubernetes API 或 etcd 存储网络配置信息。该工具非常适合需要在多节点Kubernetes集群中为容器提供简单、高效的三层网络连接场景，尤其适用于希望简化网络设置并避免复杂端口映射问题的用户。",2,"2026-06-11 03:02:27","top_language"]