system-upgrade-controller VS headscale

Rancher can do this with https://github.com/rancher/system-upgrade-controller

In theory I should use https://github.com/rancher/system-upgrade-controller, but because my homelab is still in active development and I keep nuking it, I never had a chance to upgrade lol

I'm currently bumping the versions manually, but I plan to automate that with system upgrade controller [1] and Dependabot [2] (or similar)

[1]: https://github.com/rancher/system-upgrade-controller

[2]: https://github.com/dependabot

Updating k3s is much easier using their system upgrade controller. I've been using it for a year and no hiccups. Runs in cluster, updates automatically depending on what release channel you want to use.

headscale - Open source implementation of Tailscale control server. Can be used with Tailscale's official open source client. Written in Go.

Headscale

You can always use headscale. https://github.com/juanfont/headscale

One more thing, you can host Tailscale Control Server yourself if you want, which is a plus.

https://github.com/juanfont/headscale not to mention but Tailscale has a very good culture, I’m sure they would give notice if they pull the rug. There are also many alternatives such as Zerotier and more are showing up every day and open source options.

How about self-hosted Tailscale, known as Headscale

Would be nice if https://github.com/juanfont/headscale can be managed by the Tailscale operator.

You can run your own "head scale" control server and use their clients with it: https://github.com/juanfont/headscale

Requires a lot more setup, but it is an option. I've been self-hosting headscale for some time and it is quite stable.

There's an alternative to tailscale service called headscale https://github.com/juanfont/headscale (CLI only server compatible with official tailscale clients)