From: Pete Birley <pete@port.direct>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: [WireGuard] Kubernetes/Neutron support
Date: Mon, 18 Jul 2016 14:57:49 +0100 [thread overview]
Message-ID: <1468850269.6953.2@smtp.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1319 bytes --]
Hi,
I'm investigating using Wireguard to provide a network solution for
Kubernetes via a CNI or exec network driver - has anyone done anything
on this already?
We currently have about 500 pods, on 30 nodes, in our production
cluster (though plan to scale to about 20-30 times this), and use a
combination of OpenvSwitch (gre+IPsec tunnels between hosts) and
Flannel (Each host has a sub-net on a standard Linux bridge) to provide
connectivity. Though need to both improve availability and east-west
traffic distribution, especially when pods may be located is different
geographic regions, and are migrating to a solution based on OpenStack
Neutron with Dragonflow as the SDN layer.
Does anyone have any advice on the best way to implement such a
solution? We plan to implement a reasonably 'intelligent' strategy
where by our Neutron plugin identifies the most appropriate link for
each compute node, and so expect WireGuard to only be utilized for
inter-dc connections. In particular any input on the number of
connections a single node can take (ie full-mesh style topology),
before dedicated network nodes and a hub and spoke topology makes
sense? Any advice would be appreciated, and if we find that Wireguard
fits our needs then I'd love to get involved in the project.
Cheers
Pete Birley
[-- Attachment #2: Type: text/html, Size: 1449 bytes --]
next reply other threads:[~2016-07-18 13:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 13:57 Pete Birley [this message]
2016-07-22 12:44 ` [WireGuard] Kubernetes/Neutron support Jason A. Donenfeld
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=1468850269.6953.2@smtp.gmail.com \
--to=pete@port.direct \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.