diff options
| author | Prashanth Balasubramanian <beeps@google.com> | 2015-11-21 17:37:32 -0800 |
|---|---|---|
| committer | gmarek <gmarek@google.com> | 2015-11-25 09:42:59 +0100 |
| commit | 1ca8a8d8ff7e8dd27c091dc96c7c2ff3d9f8eb55 (patch) | |
| tree | c148ca6475f3ece46231a0f887df2c4c0e219185 | |
| parent | a38708307b586f96acd615baabc23c1b7944eb72 (diff) | |
Flannel server in static pod with private etcd.
| -rw-r--r-- | flannel-integration.md | 35 |
1 files changed, 35 insertions, 0 deletions
diff --git a/flannel-integration.md b/flannel-integration.md new file mode 100644 index 00000000..5f33ec30 --- /dev/null +++ b/flannel-integration.md @@ -0,0 +1,35 @@ +# Flannel integration with Kubernetes + +## Why? + +* Networking works out of the box. +* Cloud gateway configuration is regulated. +* Consistent bare metal and cloud experience. +* Lays foundation for integrating with networking backends and vendors. + +# How? + +``` +Master Node1 +---------------------|-------------------------------- +database | + | | +{10.250.0.0/16} | docker + | here's podcidr |restart with podcidr +apiserver <------------------- kubelet + | | |here's podcidr +flannel-server:10253 <------- flannel-daemon + --/16---> + <--watch-- [config iptables] + subscribe to new node subnets + --------> [config VXLan] + | +``` + +There is a tiny lie in the above diagram, as of now, the flannel server on the master maintains a private etcd. This will not be necessary once we have a generalized network resource, and a Kubernetes x flannel backend. + +# Limitations + +* Integration is experimental + +# Wishlist |