Anmelden
golang
/
flannel
1
0
Fork 0
Dateien Issues 0 Pull-Requests 0 Wiki

Keine Beschreibung

Struktur: 960b3243b9
Branches Tags
flannel
Brandon Philips 960b3243b9 MAINTAINERS: remove @philips vor 5 Jahren
.github b10f969af4 Comment out the PR template message and add release note section vor 7 Jahren
Documentation 3f7d3e6c24 Fix typo and invalid indent in kube-flannel.yml vor 5 Jahren
backend 16b0fe6628 Merge pull request #1140 from ksubrmnn/nonpersistent vor 5 Jahren
dist 5224604055 prevent e2e tests to reuse etcd network config of previous tests vor 5 Jahren
images 91e44c4081 Add support for multiarch e2e tests vor 7 Jahren
logos 170fd5de88 logos: resized for readme vor 9 Jahren
network 0d7b99460b Use iptables --random-fully when available vor 6 Jahren
pkg 101c2116ab Fix function comments based on best practices from Effective Go vor 6 Jahren
subnet cdcef37354 Needs to clear NodeNetworkUnavailable flag on Kubernetes vor 5 Jahren
vendor 7a8088e017 Fix glide vor 5 Jahren
version cbac427350 Version embedding for Go 1.4 and 1.5 vor 9 Jahren
.appveyor.yml 145a4a48dc backend: Get flannel building on windows with stubs vor 7 Jahren
.dockerignore a8972ad5cd BUILDS: Overhaul build process vor 8 Jahren
.gitignore 8a5dd04f72 flannel: Get flannel running on windows vor 7 Jahren
.travis.yml 7a8088e017 Fix glide vor 5 Jahren
CONTRIBUTING.md c1c060c005 Added boilerplate files vor 10 Jahren
DCO c1c060c005 Added boilerplate files vor 10 Jahren
Dockerfile.amd64 a2e83950cf Fix up: missing wireguard-tools, build error vor 5 Jahren
Dockerfile.arm a2e83950cf Fix up: missing wireguard-tools, build error vor 5 Jahren
Dockerfile.arm64 a2e83950cf Fix up: missing wireguard-tools, build error vor 5 Jahren
Dockerfile.ppc64le a2e83950cf Fix up: missing wireguard-tools, build error vor 5 Jahren
Dockerfile.s390x a2e83950cf Fix up: missing wireguard-tools, build error vor 5 Jahren
LICENSE c1c060c005 Added boilerplate files vor 10 Jahren
MAINTAINERS 960b3243b9 MAINTAINERS: remove @philips vor 5 Jahren
Makefile 7a8088e017 Fix glide vor 5 Jahren
NOTICE c1c060c005 Added boilerplate files vor 10 Jahren
OWNERS ae4144090b New maintainers and reviewers. Creating an owners file that the ci-bots can work with. vor 6 Jahren
README.md ff825f7a00 edit Flannel license info so that GitHub recognizes it vor 6 Jahren
bill-of-materials.json 22d406b596 bill-of-materials: initial commit vor 7 Jahren
bill-of-materials.override.json 22d406b596 bill-of-materials: initial commit vor 7 Jahren
code-of-conduct.md 6695a0202b update CoC vor 7 Jahren
glide.lock 7a8088e017 Fix glide vor 5 Jahren
glide.yaml 3231210712 Fix typo in glide.yaml vor 6 Jahren
header-check.sh ff825f7a00 edit Flannel license info so that GitHub recognizes it vor 6 Jahren
main.go 477d9fa153 Use publicIP lookup iface if --public-ip indicated vor 5 Jahren
packet-01.png 82195b1cc4 diagram: update to reflect name change vor 10 Jahren

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.