Tom Denham
bd001e1c39
backend/vxlan: Add support for "direct routing"
|
7 tahun lalu | |
|---|---|---|
| .github | 7 tahun lalu | |
| Documentation | 7 tahun lalu | |
| backend | 7 tahun lalu | |
| dist | 7 tahun lalu | |
| logos | 9 tahun lalu | |
| network | 7 tahun lalu | |
| pkg | 7 tahun lalu | |
| subnet | 7 tahun lalu | |
| vendor | 7 tahun lalu | |
| version | 9 tahun lalu | |
| .dockerignore | 8 tahun lalu | |
| .gitignore | 8 tahun lalu | |
| .travis.yml | 8 tahun lalu | |
| CONTRIBUTING.md | 10 tahun lalu | |
| DCO | 10 tahun lalu | |
| Dockerfile.amd64 | 7 tahun lalu | |
| Dockerfile.arm | 8 tahun lalu | |
| Dockerfile.arm64 | 8 tahun lalu | |
| Dockerfile.ppc64le | 8 tahun lalu | |
| Dockerfile.s390x | 8 tahun lalu | |
| LICENSE | 10 tahun lalu | |
| MAINTAINERS | 8 tahun lalu | |
| Makefile | 7 tahun lalu | |
| NOTICE | 10 tahun lalu | |
| README.md | 7 tahun lalu | |
| bill-of-materials.json | 7 tahun lalu | |
| bill-of-materials.override.json | 7 tahun lalu | |
| glide.lock | 7 tahun lalu | |
| glide.yaml | 7 tahun lalu | |
| license-check.sh | 8 tahun lalu | |
| main.go | 7 tahun lalu | |
| packet-01.png | 10 tahun lalu |
README.md
flannel
Flannel is a simple and easy to configure 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 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 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. For network policy, other projects such as Calico can be used.
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, CoreOS's Tectonic sets up flannel in the Kubernetes clusters it creates using the open source Tectonic 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.
See Kubernetes for more details.
Getting started on Docker
flannel 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
- Building (and releasing)
- Configuration
- Backends
- Running
- Troubleshooting
- Projects integrating with flannel
- Production users
Contact
- Mailing list: coreos-dev
- IRC: #coreos on freenode.org
- Slack: #flannel on Calico Users Slack
- Planning/Roadmap: milestones, roadmap
- Bugs: issues
Contributing
See CONTRIBUTING for details on submitting patches and the contribution workflow.
Reporting bugs
See reporting bugs for details about reporting any issues.
License
Flannel is under the Apache 2.0 license. See the LICENSE file for details.