Masuk
golang
/
flannel
1
0
Fork 0
Berkas Masalah 0 Permintaan Tarik 0 Wiki

Tidak Ada Deskripsi

Pohon: be073e831a
Ranting Tag
flannel
Luther Monson be073e831a upgrade to go1.15.5 4 tahun lalu
.github b10f969af4 Comment out the PR template message and add release note section 7 tahun lalu
Documentation aedcbade5a Merge pull request #1227 from pain400/pain400-patch-troubleshooting-file 4 tahun lalu
backend 385faf9623 Merge pull request #1215 from adelina-t/fix_vni_windows 4 tahun lalu
dist 70b109514b Add and implement iptables-wrapper-installer.sh from https://github.com/kubernetes-sigs/iptables-wrappers 4 tahun lalu
images 8477bba6a1 use alpine 3.12 everywhere 4 tahun lalu
logos 170fd5de88 logos: resized for readme 9 tahun lalu
network 1850b09185 iptables: handle errors that prevent rule deletes 5 tahun lalu
pkg d31b0dc85a windows: replace old netsh (rakelkar/gonetsh) with powershell commands 4 tahun lalu
subnet bd3f2c0715 Update release-tests harness to match latest k8s and etcd 5 tahun lalu
vendor 5dc1ff6e0f switch to go modules 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 be073e831a upgrade to go1.15.5 4 tahun lalu
CONTRIBUTING.md c1c060c005 Added boilerplate files 10 tahun lalu
DCO c1c060c005 Added boilerplate files 10 tahun lalu
Dockerfile.amd64 6cd8b162fc Merge pull request #1290 from PascalBourdier/CVE-2019-14697 4 tahun lalu
Dockerfile.arm 0a5fca3daf Add --no-sanity-check to iptables-wrapper-installer.sh for architectures other than amd64 4 tahun lalu
Dockerfile.arm64 0a5fca3daf Add --no-sanity-check to iptables-wrapper-installer.sh for architectures other than amd64 4 tahun lalu
Dockerfile.ppc64le 0a5fca3daf Add --no-sanity-check to iptables-wrapper-installer.sh for architectures other than amd64 4 tahun lalu
Dockerfile.s390x 0a5fca3daf Add --no-sanity-check to iptables-wrapper-installer.sh for architectures other than amd64 4 tahun lalu
LICENSE c1c060c005 Added boilerplate files 10 tahun lalu
MAINTAINERS 960b3243b9 MAINTAINERS: remove @philips 5 tahun lalu
Makefile be073e831a upgrade to go1.15.5 4 tahun lalu
NOTICE c1c060c005 Added boilerplate files 10 tahun lalu
OWNERS ce699f7db0 New reviewers to OWNERS file 4 tahun lalu
README.md 8a1bcf6f2b Modify kube-flannel.yaml to use rbac.authorization.k8s.io/v1 4 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
go.mod be073e831a upgrade to go1.15.5 4 tahun lalu
go.sum 5dc1ff6e0f switch to go modules 4 tahun lalu
header-check.sh ff825f7a00 edit Flannel license info so that GitHub recognizes it 6 tahun lalu
main.go 117c10277e pass waitgroup pointer 4 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.17+ 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

Community Meeting

The Flannel Maintainer Community runs a meeting on every other Thursday at 8:30 AM PST. This meeting is used to discuss issues, open pull requests, and other topics related to Flannel should the need arise.

The meeting agenda and Zoom link can be found here: Flannel Community Meeting Agneda

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.