3 ms·
> - internal network only with edge nodes (i.e tail scale out the box, + some edge nodes) Can you help me understand that? > - option to deploy on multiple se
by hunvreus 1y ago
> - internal network only with edge nodes (i.e tail scale out the box, + some edge nodes)
Can you help me understand that?
> - option to deploy on multiple servers to scale with super simple non k8s approach.
I'm working on that, allowing you to manage remote nodes from a single /dev/push instance.
- hhthrowaway1230 1y ago> Can you help me understand that? Like 10 nodes behind tailscale/wireguard in a private network, with only 2 nodes where you have a port open on 80/443, those are exposed to the public network. The rest of the nodes are all private like db, redis, etc etc.
- hunvreus 1y agoStill figuring it out. Routing the traffic is the annoying bit.
- hhthrowaway1230 1y agoGuess that is why there isn't an easy go to solution yet. But it's well needed.
- psviderski 1y agoCheck out https://github.com/psviderski/uncloud https://github.com/psviderski/uncloud I'm building. Multi-machine deployments and a private WireGuard network spanning locations (even behind a NAT) are its core capabilities.