Nessuna descrizione

phantooom bb8aaa6dad fix typo 7 anni fa
.github b10f969af4 Comment out the PR template message and add release note section 7 anni fa
Documentation 8479f7e76a Correct spelling "reposistory" 7 anni fa
backend bb8aaa6dad fix typo 7 anni fa
dist 59ab6afa56 Lots of fixes getting it ready to merge (tests/docs) 7 anni fa
images 91e44c4081 Add support for multiarch e2e tests 7 anni fa
logos 170fd5de88 logos: resized for readme 9 anni fa
network 454afbe127 Added new flag -iptables-resync allows you to pass an int (default 5) that is used in network/iptables SetupAndEnsureIPTables to control how often it resync's the iptables rules. We found on a larger cluster that having this value hardcoded to 5 seconds created too much contention on the iptables lock for kube-proxy to properly function 7 anni fa
pkg e0ca38e8fd Merge pull request #911 from tomdee/rakelkar-jroggeman/windows_impl 7 anni fa
subnet e8e4de7513 Merge pull request #896 from tomdee/fix-subnet-checking 7 anni fa
vendor 6b98346d93 Merge pull request #929 from tomdee/feature/ipsec 7 anni fa
version cbac427350 Version embedding for Go 1.4 and 1.5 9 anni fa
.appveyor.yml 145a4a48dc backend: Get flannel building on windows with stubs 7 anni fa
.dockerignore a8972ad5cd BUILDS: Overhaul build process 8 anni fa
.gitignore 8a5dd04f72 flannel: Get flannel running on windows 7 anni fa
.travis.yml 0845f923cc travis: Only run the tests once 7 anni fa
CONTRIBUTING.md c1c060c005 Added boilerplate files 10 anni fa
DCO c1c060c005 Added boilerplate files 10 anni fa
Dockerfile.amd64 475eaf919a Fix up rebase 7 anni fa
Dockerfile.arm 475eaf919a Fix up rebase 7 anni fa
Dockerfile.arm64 475eaf919a Fix up rebase 7 anni fa
Dockerfile.ppc64le 475eaf919a Fix up rebase 7 anni fa
Dockerfile.s390x 475eaf919a Fix up rebase 7 anni fa
LICENSE c1c060c005 Added boilerplate files 10 anni fa
MAINTAINERS c2171f9dc5 MAINTAINERS: remove steevej 8 anni fa
Makefile 5cd6069683 Builds: Update go to v1.9.2 7 anni fa
NOTICE c1c060c005 Added boilerplate files 10 anni fa
README.md 014b2d52df Add portmap plugin to CNI conf 7 anni fa
bill-of-materials.json 22d406b596 bill-of-materials: initial commit 7 anni fa
bill-of-materials.override.json 22d406b596 bill-of-materials: initial commit 7 anni fa
code-of-conduct.md 6695a0202b update CoC 7 anni fa
glide.lock 6b98346d93 Merge pull request #929 from tomdee/feature/ipsec 7 anni fa
glide.yaml 9a83d0bdcf Apply changes to etcdv2 code after package move 7 anni fa
license-check.sh a8972ad5cd BUILDS: Overhaul build process 8 anni fa
main.go 7bc417bfe1 Fixed typo in arguments parser 7 anni fa
packet-01.png 82195b1cc4 diagram: update to reflect name change 10 anni fa

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