From: Tom Denham <tom@tigera.io>
To: WireGuard@lists.zx2c4.com
Subject: Using WireGuard with Kubernetes
Date: Wed, 25 Apr 2018 10:54:06 -0700 [thread overview]
Message-ID: <CAJ5-c6WjxshZF7sE98Sk8XYr=9o5vRAiLQ+xCwq2Nidt8iPU8g@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 730 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 822 bytes --]
next reply other threads:[~2018-04-25 17:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 17:54 Tom Denham [this message]
2018-04-25 20:15 ` Martin Eskdale Moen
2018-04-25 23:32 ` Tom Denham
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ5-c6WjxshZF7sE98Sk8XYr=9o5vRAiLQ+xCwq2Nidt8iPU8g@mail.gmail.com' \
--to=tom@tigera.io \
--cc=WireGuard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).