Score:0

Should I use an existing WireGuard connection as basis for a K8S CNI plugin?

dk flag

I'm setting up a Kubernetes cluster, where the Nodes are distributed across different networks. Additionally, all Nodes are part of a WireGuard network. Each Node therefore has 2 IP addresses, one bound to its primary NIC (private or public IPv4) and a WireGuard one.

Usually, I would have used Weave Net as CNI, but as there is already an (encrypted) WireGuard connection between the nodes, the actual question was if using a simple CNI like Flannel VXLAN or WireGuard might be a better choice, as it would reduce the overall complexity.

Do you have any experience on relying on an existing VPN as transport for a CNI, or do you see good reasons to not follow that approach and use a dedicated CNI connection like Weave Net instead, even though it would induce additional load on all Nodes?

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.