Re:Comparison of Networking Solutions for Kubernetes
by lobster_johnson on Friday February 19, 2016 @12:19PM
(#11134815)
ipvlan sounds great, but I'm not a networking guru, and I'm missing a lot of pieces. Do you know of any documentation that explains it at both a high and low level, and shows the steps needed to cluster a bunch of nodes together (say, on a cloud provider where you only have public IPs) in a single virtual LAN?
In the post you mentioned one of the drawbacks to adopting ipvlan was the lack of tooling to manage it. To address this issue, and a few others[2], Kubernetes has recently adopted the Container Network Interface(CNI)[3] standard as the solution for managing network plugins in Kubernetes. CNI ships with a few plugins including ipvlan and, maybe more importantly, the ability to allocate and manage IP addresses[4]. Over time CNI should give Kubernetes the flexibility to work well with multiple container runtimes including Docker and rkt, while allowing third party solutions to fill in the gaps around networking.
[1] https://www.kernel.org/doc/Documentation/networking/ipvlan.t...
[2] http://blog.kubernetes.io/2016/01/why-Kubernetes-doesnt-use-...
[3] https://github.com/appc/cni/blob/master/SPEC.md
[4] https://github.com/appc/cni/blob/master/SPEC.md#ip-allocatio...