kilo VS Netmaker

For the particular case of creating a wireguard mesh network in kubernetes, I've been quite happy with Kilo[0]. Does anyone with experience in both kilo and netmaker know how they compare?

[0]: https://kilo.squat.ai/

Then using something like this: https://docs.tigera.io/calico-enterprise/latest/compliance/encrypt-cluster-pod-traffic#value or: https://github.com/squat/kilo

Another one for the alternatives list is Kilo[1]

It's a wireguard based kubernetes network overlay. I use it to access private services in my homelab cluster from my laptop, phone, etc.

[1] https://kilo.squat.ai

Sorry, big typo, I meant "Kilo" and not "Silo"...

Networking: Manually configured wireguard VPN between all nodes. I consider checking out kilo when I find some time though. VPS handles all incoming traffic (with ingress-nginx) but outbound traffic from containers uses regular network, no VPN.

Kilo — Wireguard-based multi-cloud overlay

Netmaker - Layer 3 peer-to-peer overlay network and private DNS. Similar to Tailscale, but with a self-hosted server/admin UI. Runs kernel WireGuard so very fast. Not FOSS, but the source code is available. Written in Go.

My plan is to set up an EC2 instance and host a VPN, considering options like Netmaker, OpenVPN, or Tailscale. The goal is to connect these devices to the VPN, enabling SSH access from any connected node. This method seems cost-effective(Considering I want to use 100s of devices and potentially 1000s) and straightforward, requiring a simple setup with a sudo apt command on the Raspberry Pi.

I'm wondering if there are any alternative approaches to achieve this. Is something like Netmaker or Tailscale feasible enough? If you have any suggestions, I'd greatly appreciate it.

https://github.com/gravitl/netmaker

Honorable mention:

SuperHighway84 - more of a Usenet-inspired darknet, but I love the concept + the author's personal website:

https://github.com/mrusme/superhighway84

Exciting news to share! Netmaker has officially embraced open source. This momentous decision was unveiled at the Open Source Summit in Europe when the pull request successfully merged, transitioning their server from the SSPL to the widely recognized Apache License 2.0.

While we've encountered some challenges and worked with vendors like Cisco to find solutions, I'm curious about recommendations for SD-WAN providers that are well-suited for SASE users. This includes not only Zscaler but also other options like Netmaker, Palo Alto, Cloudflare, Cisco, and Forcepoint.

Now, my main question is how I can link my DDNS host endpoint with my EC2 instances, allowing only my home network to access them. I've come across a variety of suggestions, such as Netmaker, OpenVPN, Tailscale etc. but I'm curious to hear your opinions on these solutions.

HN is somehow always timely. Currently, these folks expect me to sign a CLA for a one-byte change to their README: https://github.com/gravitl/netmaker/pull/2516