From: Raffaele Spazzoli <rspazzol@redhat.com>
To: wireguard@lists.zx2c4.com
Subject: wireguard and OpenShift SDN mesh
Date: Tue, 6 Nov 2018 17:30:55 -0500 [thread overview]
Message-ID: <CACOeLqJ2r5ZG+23mt4So8G1ukCQR3g67x-LgMHZo0RjKJYCiBg@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 566 bytes --]
Hi,
I wanted to share that I have come up a method to create a wireguard mesh
for a set of OpenShift clusters. If interested more details can be found
here:
https://blog.openshift.com/connecting-multiple-openshift-sdns-with-a-network-tunnel/
https://blog.openshift.com/connecting-multiple-openshift-sdns-with-a-network-tunnel-part-2-service-proxying-and-discovery/
Thanks,
Raffaele
Raffaele Spazzoli
Senior Architect - OpenShift <https://www.openshift.com>, Containers
and PaaS Practice <https://www.redhat.com/en/services/consulting/paas>
Tel: +1 216-258-7717
[-- Attachment #1.2: Type: text/html, Size: 1371 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
reply other threads:[~2018-11-06 22:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CACOeLqJ2r5ZG+23mt4So8G1ukCQR3g67x-LgMHZo0RjKJYCiBg@mail.gmail.com \
--to=rspazzol@redhat.com \
--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).