Using WireGuard with Kubernetes

[Martin Eskdale Moen]

I've been doing some experiments with this. Not so much with kubes yet,
that was next on the list.
I think at the moment linking together the various network namespaces using
a linux bridge should work.
Not sure if I'm shooting myself in the foot at all using linux bridges.
Reading over the docs of openvswitch vs linux bridge it seems the bridge is
easier to understand and overall more useful.

On Wed, Apr 25, 2018 at 6:54 PM, Tom Denham <tom at tigera.io> wrote:

> I was wondering if anyone had any experience using WireGuard with
> Kubernetes? I see that the WireGuard website says "Ready for Containers"
> but the model it describes sounds like it would work for adding WireGuard
> to a single container (putting the wg interface in the container itself).
> If I have many containers on a host, and many containers on a host, and I
> want them all to be able to communicate with each other using WireGuard,
> then I would need to create many different WireGuard interfaces and
> presumably they would all need their own independent config. It doesn't
> feel like this would scale to 100's of hosts and tens of thousands of
> containers.
>
> I'm interested in hearing people's thoughts and ideas on this
> Thanks
> Tom
>
> _______________________________________________
> WireGuard mailing list
> WireGuard at lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.zx2c4.com/pipermail/wireguard/attachments/20180425/fbdec056/attachment.html>