3 ms·
This is more or less what Calico does: https://docs.projectcalico.org/v3.1/introduction/ https://docs.projectcalico.org/v3.1/introduction/ http://leebriggs.co
by twic 9y ago
This is more or less what Calico does:
https://docs.projectcalico.org/v3.1/introduction/ https://docs.projectcalico.org/v3.1/introduction/
http://leebriggs.co.uk/blog/2017/02/18/kubernetes-networking-calico.html http://leebriggs.co.uk/blog/2017/02/18/kubernetes-networking...
In a Calico setup, every container (or VM - they use the term "workload" to abstract over the two) has an IP address, and talks to other containers in the usual way. AIUI, Calico does a couple of things to make that work at Cloud Scale (tm): it pushes firewall rules into the kernel, to make sure each container can only communicate with the other containers it's supposed to, and it propagates routes around, so each host knows where to send packets destined for containers on other hosts.
The routing bit is important because Calico is designed to run as a flat IP space on top of a non-flat ethernet space, ie one where the access switches are connected by routers rather than more switches. That's useful because scaling a flat ethernet network up to a huge size is apparently hard (network engineers start telling horror stories about Spanning Tree Protocol etc).
Calico still has more moving parts than i'm personally comfortable with, but it seems broadly sensible.