https://github.com/y1r/flannel-srv6
Proof-of-Concept of Kubernetes CNI with SRv6 backend
https://github.com/y1r/flannel-srv6
cni flannel kubernetes segment-routing srv6
Last synced: 8 months ago
JSON representation
Proof-of-Concept of Kubernetes CNI with SRv6 backend
- Host: GitHub
- URL: https://github.com/y1r/flannel-srv6
- Owner: y1r
- License: apache-2.0
- Created: 2020-03-07T07:05:15.000Z (almost 6 years ago)
- Default Branch: srv6
- Last Pushed: 2020-03-18T01:41:35.000Z (almost 6 years ago)
- Last Synced: 2024-05-02T01:51:08.955Z (over 1 year ago)
- Topics: cni, flannel, kubernetes, segment-routing, srv6
- Language: Go
- Homepage:
- Size: 45.9 MB
- Stars: 7
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
- Code of conduct: code-of-conduct.md
Awesome Lists containing this project
README
# A proof-of-concept of flannel with SRv6 Backend
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](https://developers.cyberagent.co.jp/blog/archives/25394/).
This work was conducted as an internship of [@CyberAgent](https://github.com/CyberAgent).
## How to use
- Build an image and push to a docker registry.
- Change `kube-flannel.yml` to use `srv6` backend (`vxlan` -> `srv6`).
- Deploy `flanneld` to your Kubernetes cluster, that its worker node is connected in the same subnet.
---
# flannel
[](https://travis-ci.org/coreos/flannel)
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][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][backends] 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][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][tectonic] sets up flannel in the Kubernetes clusters it creates using the open source [Tectonic Installer][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](Documentation/kubernetes.md) 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/running.md)
## Documentation
- [Building (and releasing)](Documentation/building.md)
- [Configuration](Documentation/configuration.md)
- [Backends](Documentation/backends.md)
- [Running](Documentation/running.md)
- [Troubleshooting](Documentation/troubleshooting.md)
- [Projects integrating with flannel](Documentation/integrations.md)
- [Production users](Documentation/production-users.md)
## Contact
* Mailing list: coreos-dev
* IRC: #coreos on freenode.org
* Slack: #flannel on [Calico Users Slack](https://slack.projectcalico.org)
* Planning/Roadmap: [milestones][milestones], [roadmap][roadmap]
* Bugs: [issues][flannel-issues]
## Contributing
See [CONTRIBUTING][contributing] for details on submitting patches and the contribution workflow.
## Reporting bugs
See [reporting bugs][reporting] for details about reporting any issues.
## Licensing
Flannel is under the Apache 2.0 license. See the [LICENSE][license] file for details.
[calico]: http://www.projectcalico.org
[pod-cidr]: https://kubernetes.io/docs/admin/kubelet/
[etcd]: https://github.com/coreos/etcd
[contributing]: CONTRIBUTING.md
[license]: https://github.com/coreos/flannel/blob/master/LICENSE
[milestones]: https://github.com/coreos/flannel/milestones
[flannel-issues]: https://github.com/coreos/flannel/issues
[backends]: Documentation/backends.md
[roadmap]: https://github.com/kubernetes/kubernetes/milestones
[reporting]: Documentation/reporting_bugs.md
[tectonic-installer]: https://github.com/coreos/tectonic-installer
[installing-with-kubeadm]: https://kubernetes.io/docs/getting-started-guides/kubeadm/
[tectonic]: https://coreos.com/tectonic/