Açıklama Yok

Tom Denham 4485ecd413 subnet/config.go: Fix handling of subnet config 7 yıl önce
.github b10f969af4 Comment out the PR template message and add release note section 7 yıl önce
Documentation 8c397dc873 kube: Update manifests to v0.9.1 7 yıl önce
backend 145a4a48dc backend: Get flannel building on windows with stubs 7 yıl önce
dist 9d1a5720c4 Fix e2e tests for non-amd64 archs 7 yıl önce
images 91e44c4081 Add support for multiarch e2e tests 7 yıl önce
logos 170fd5de88 logos: resized for readme 9 yıl önce
network 145a4a48dc backend: Get flannel building on windows with stubs 7 yıl önce
pkg 145a4a48dc backend: Get flannel building on windows with stubs 7 yıl önce
subnet 4485ecd413 subnet/config.go: Fix handling of subnet config 7 yıl önce
vendor c9970d0569 Allow kube subnet manager to run outside of kubernetes 7 yıl önce
version cbac427350 Version embedding for Go 1.4 and 1.5 9 yıl önce
.appveyor.yml 145a4a48dc backend: Get flannel building on windows with stubs 7 yıl önce
.dockerignore a8972ad5cd BUILDS: Overhaul build process 8 yıl önce
.gitignore 145a4a48dc backend: Get flannel building on windows with stubs 7 yıl önce
.travis.yml 0845f923cc travis: Only run the tests once 7 yıl önce
CONTRIBUTING.md c1c060c005 Added boilerplate files 10 yıl önce
DCO c1c060c005 Added boilerplate files 10 yıl önce
Dockerfile.amd64 3e883b809e Makefile: Cleanup, alpine and amd64 only UDP 7 yıl önce
Dockerfile.arm 3e883b809e Makefile: Cleanup, alpine and amd64 only UDP 7 yıl önce
Dockerfile.arm64 3e883b809e Makefile: Cleanup, alpine and amd64 only UDP 7 yıl önce
Dockerfile.ppc64le 3e883b809e Makefile: Cleanup, alpine and amd64 only UDP 7 yıl önce
Dockerfile.s390x 3e883b809e Makefile: Cleanup, alpine and amd64 only UDP 7 yıl önce
LICENSE c1c060c005 Added boilerplate files 10 yıl önce
MAINTAINERS c2171f9dc5 MAINTAINERS: remove steevej 8 yıl önce
Makefile 9d1a5720c4 Fix e2e tests for non-amd64 archs 7 yıl önce
NOTICE c1c060c005 Added boilerplate files 10 yıl önce
README.md 7980309926 README.md: fix link to kubernetes documentation 7 yıl önce
bill-of-materials.json 22d406b596 bill-of-materials: initial commit 7 yıl önce
bill-of-materials.override.json 22d406b596 bill-of-materials: initial commit 7 yıl önce
glide.lock c9970d0569 Allow kube subnet manager to run outside of kubernetes 7 yıl önce
glide.yaml c9970d0569 Allow kube subnet manager to run outside of kubernetes 7 yıl önce
license-check.sh a8972ad5cd BUILDS: Overhaul build process 8 yıl önce
main.go 5df82dcbcb network/iptables: Add iptables rules to FORWARD chain 7 yıl önce
packet-01.png 82195b1cc4 diagram: update to reflect name change 10 yıl önce

README.md

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 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.

For Kubernetes v1.6+ kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml

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

Contact

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.