kilo VS inlets-pro

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

I created this because of my frustration with inlets.

On one hand, this is about inlets, a product I wrote to help developers, self-hosters and enterprises to connect containers to the cloud. On the other hand, I hope you'll learn as much as I did about Proxy Protocol and how hard it is to configure for Traefik behind K3s.

How does this compare with ngrok, localtunnel, or Inlets?

It's unfortunate the only mature open source alternative[1] went on a path to seriously expensive subscriptions, 5x of a tailscale personal subscription.

[1]: https://inlets.dev/

Be specific. There are plenty of services I pay for, such as WebStorm, Photoshop, TablePlus, etc. Look at how JetBrains or TablePlus talks about their product. Take a look at inlets for a smaller scale sales pattern.