2 ms·

I'm still unconvinced "adding kubernetes" is likely to make simple setup simpler - but to each their own. But regarding kilo - doesn't sound like it makes much

by e12e 6y ago

I'm still unconvinced "adding kubernetes" is likely to make simple setup simpler - but to each their own. But regarding kilo - doesn't sound like it makes much sense for laptop/road warrior? https://github.com/squat/kilo#step-4-ensure-nodes-have-public-ip https://github.com/squat/kilo#step-4-ensure-nodes-have-publi... > At least one node in each location must have an IP address that is routable from the other locations. If the locations are in different clouds or private networks, then this must be a public IP address. Makes it difficult to use you laptop from a coffee shop?

rektide 6y ago
I'm running into this problem now, trying to set up my laptop as a k3s node. I'm still exploring my options, but I probably have to hand-wire up WireGuard on the roadwarrior nodes manually, & I hope/think that might be sufficient, but haven't tried yet. There is a great VPN mode[1] in Kilo, if I just wanted to connect my laptops or workstations to the k3s cluster. [1] https://github.com/squat/kilo https://github.com/squat/kilo
- e12e 6y ago
  Might be worth looking into zerotier if what you need is transparent mesh vpn with fairly smart routing (local lan traffic stays local). Never tried to combine it with k8s, so ymmv.