In a previous post I wrote about using ZeroTier for my homelab and mentioned I ended up writing two scripts:

• one for joining a network and authorizing the new device
• another for creating DNS entries in DNSMASQ for DNS lookup

This first part will focus on how I join my new servers to my ZeroTier labnetwork. For more information about ZeroTier in general go read my other post that go in much more detail about that. Part two about DNS for ZeroTier will soon be available.

Lets get started!

I have started to test out ZeroTier as an alternative to traditional VPN for my home lab. I’m not unhappy about how VPN works with my Ubiquity USG setup, but I need something more intrinsic and independant of whereever my workloads would run and not depend on a connection to homelap or me connecting to it for access to these. In my opinion VPN is great for high performance site-to-site tunnels or for roadworkers out and about needing to connect to the “office/data center” i.e some aggregate of workloads in close proximity. They’re not well suited for scattered ephemeral workloads and I do not want to maintain scripting handeling a cumpersome setup processes for each new VM/contrainer or VPN site-to-site tunnels between my homelab, worklab and a couple of public cloud providers (those guys even charge for VPN connections). For my requirements a simple to setup and encrypted overlay solution is a far better option as I tend to spin up short lived workloads on everything between my own raspberry pi cluster, worklab and clouds like AWS and Google.
There are great VPN alternatives available like WireGuard or Tinc with powerfull features not found elswhere. Though they’re still more comparable to traditional VPN - plus they’re still more complex to setup than ZeroTier.

Anyway, let dig into ZeroTier!

This is my personal blog and I will most of the time use this as a sort of parking space for thoughts and projects.
Some will be about workrelated stuff but more likely it will be about containers and Kubernetes - plus fun projects activities out and about.

Instead of using one of the more boring blog engines out on the internet (looking at you Medium, Blogger and Wordpress) I opted for a Markdown based, static generated blog framework hosted on github pages. I ended up with Hexo.io which is very much like Jekyllrb and Hugo, though something just felt more right for me with Hexo - though I could end up use Hugo if they catch up with Hexo features. I really like their approach, but Hexo had more features that resonated with me.