This repository is a proof-of-concept of SRv6 Backend for flannel, not for production use. We modified a part of this code to publish, so there is no guarantee of working and also support.
For more implementation details, please refer to our blog. This work was conducted as an internship of @CyberAgent.
- Build an image and push to a docker registry.
- Change
kube-flannel.ymlto usesrv6backend (vxlan->srv6). - Deploy
flanneldto your Kubernetes cluster, that its worker node is connected in the same subnet.
Flannel is a simple and easy way to configure a layer 3 network fabric designed for Kubernetes.
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.
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.
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.
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.
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
- Building (and releasing)
- Configuration
- Backends
- Running
- Troubleshooting
- Projects integrating with flannel
- Production users
- Mailing list: coreos-dev
- IRC: #coreos on freenode.org
- Slack: #flannel on Calico Users Slack
- Planning/Roadmap: milestones, roadmap
- Bugs: issues
See CONTRIBUTING for details on submitting patches and the contribution workflow.
See reporting bugs for details about reporting any issues.
Flannel is under the Apache 2.0 license. See the LICENSE file for details.