Tidak Ada Deskripsi

Rajat Chopra 84243d0775 Merge pull request #1319 from Oats87/gofmt 4 tahun lalu
.github b10f969af4 Comment out the PR template message and add release note section 7 tahun lalu
Documentation c2e0b388a5 Merge pull request #1269 from knight42/doc/awsvpc 4 tahun lalu
backend 22aeaf0db6 Run gofmt -w on backend/vxlan/device.go to pass CI 4 tahun lalu
dist bd3f2c0715 Update release-tests harness to match latest k8s and etcd 5 tahun lalu
images 91e44c4081 Add support for multiarch e2e tests 7 tahun lalu
logos 170fd5de88 logos: resized for readme 9 tahun lalu
network 0d7b99460b Use iptables --random-fully when available 6 tahun lalu
pkg 101c2116ab Fix function comments based on best practices from Effective Go 6 tahun lalu
subnet bd3f2c0715 Update release-tests harness to match latest k8s and etcd 5 tahun lalu
vendor e2f31ac266 Disabling ipv6 accept_ra explicitely on the created interface 4 tahun lalu
version cbac427350 Version embedding for Go 1.4 and 1.5 9 tahun lalu
.appveyor.yml 145a4a48dc backend: Get flannel building on windows with stubs 7 tahun lalu
.dockerignore a8972ad5cd BUILDS: Overhaul build process 8 tahun lalu
.gitignore 8a5dd04f72 flannel: Get flannel running on windows 7 tahun lalu
.travis.yml 7a8088e017 Fix glide 5 tahun lalu
CONTRIBUTING.md c1c060c005 Added boilerplate files 10 tahun lalu
DCO c1c060c005 Added boilerplate files 10 tahun lalu
Dockerfile.amd64 a2e83950cf Fix up: missing wireguard-tools, build error 5 tahun lalu
Dockerfile.arm a2e83950cf Fix up: missing wireguard-tools, build error 5 tahun lalu
Dockerfile.arm64 a2e83950cf Fix up: missing wireguard-tools, build error 5 tahun lalu
Dockerfile.ppc64le a2e83950cf Fix up: missing wireguard-tools, build error 5 tahun lalu
Dockerfile.s390x a2e83950cf Fix up: missing wireguard-tools, build error 5 tahun lalu
LICENSE c1c060c005 Added boilerplate files 10 tahun lalu
MAINTAINERS 960b3243b9 MAINTAINERS: remove @philips 5 tahun lalu
Makefile bd3f2c0715 Update release-tests harness to match latest k8s and etcd 5 tahun lalu
NOTICE c1c060c005 Added boilerplate files 10 tahun lalu
OWNERS ae4144090b New maintainers and reviewers. Creating an owners file that the ci-bots can work with. 6 tahun lalu
README.md ff825f7a00 edit Flannel license info so that GitHub recognizes it 6 tahun lalu
bill-of-materials.json 22d406b596 bill-of-materials: initial commit 7 tahun lalu
bill-of-materials.override.json 22d406b596 bill-of-materials: initial commit 7 tahun lalu
code-of-conduct.md 6695a0202b update CoC 7 tahun lalu
glide.lock 7a8088e017 Fix glide 5 tahun lalu
glide.yaml 3231210712 Fix typo in glide.yaml 6 tahun lalu
header-check.sh ff825f7a00 edit Flannel license info so that GitHub recognizes it 6 tahun lalu
main.go 477d9fa153 Use publicIP lookup iface if --public-ip indicated 5 tahun lalu
packet-01.png 82195b1cc4 diagram: update to reflect name change 10 tahun lalu

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.