Няма описание

Sebastian Sch 0106d23455 This PR adds the cni version to the cni-conf.yaml inside the kube-flannel-cfg configmap преди 5 години
.github b10f969af4 Comment out the PR template message and add release note section преди 7 години
Documentation 0106d23455 This PR adds the cni version to the cni-conf.yaml inside the kube-flannel-cfg configmap преди 5 години
backend e4deb05e97 Merge pull request #1096 from ksubrmnn/overlay преди 6 години
dist 219cb896a7 Deploy Flannel with unprivileged PSP преди 6 години
images 91e44c4081 Add support for multiarch e2e tests преди 7 години
logos 170fd5de88 logos: resized for readme преди 9 години
network 0d7b99460b Use iptables --random-fully when available преди 6 години
pkg 101c2116ab Fix function comments based on best practices from Effective Go преди 6 години
subnet 101c2116ab Fix function comments based on best practices from Effective Go преди 6 години
vendor 403cffd8d4 Update hcsshim for HostRoute policy in Windows VXLAN преди 6 години
version cbac427350 Version embedding for Go 1.4 and 1.5 преди 9 години
.appveyor.yml 145a4a48dc backend: Get flannel building on windows with stubs преди 7 години
.dockerignore a8972ad5cd BUILDS: Overhaul build process преди 8 години
.gitignore 8a5dd04f72 flannel: Get flannel running on windows преди 7 години
.travis.yml 0845f923cc travis: Only run the tests once преди 7 години
CONTRIBUTING.md c1c060c005 Added boilerplate files преди 10 години
DCO c1c060c005 Added boilerplate files преди 10 години
Dockerfile.amd64 475eaf919a Fix up rebase преди 7 години
Dockerfile.arm 475eaf919a Fix up rebase преди 7 години
Dockerfile.arm64 475eaf919a Fix up rebase преди 7 години
Dockerfile.ppc64le 475eaf919a Fix up rebase преди 7 години
Dockerfile.s390x 475eaf919a Fix up rebase преди 7 години
LICENSE c1c060c005 Added boilerplate files преди 10 години
MAINTAINERS 29fc3a782f Update MAINTAINERS преди 6 години
Makefile b398973408 Makefile: fix indentation преди 6 години
NOTICE c1c060c005 Added boilerplate files преди 10 години
OWNERS ae4144090b New maintainers and reviewers. Creating an owners file that the ci-bots can work with. преди 6 години
README.md ff825f7a00 edit Flannel license info so that GitHub recognizes it преди 6 години
bill-of-materials.json 22d406b596 bill-of-materials: initial commit преди 7 години
bill-of-materials.override.json 22d406b596 bill-of-materials: initial commit преди 7 години
code-of-conduct.md 6695a0202b update CoC преди 7 години
glide.lock 403cffd8d4 Update hcsshim for HostRoute policy in Windows VXLAN преди 6 години
glide.yaml 403cffd8d4 Update hcsshim for HostRoute policy in Windows VXLAN преди 6 години
header-check.sh ff825f7a00 edit Flannel license info so that GitHub recognizes it преди 6 години
main.go d278eb7287 Add additional logging for optional features преди 6 години
packet-01.png 82195b1cc4 diagram: update to reflect name change преди 10 години

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.

Licensing

Flannel is under the Apache 2.0 license. See the LICENSE file for details.