Getting Started
Time to get crack-a-lacking! But first…better make sure you’ve got all the tools you’ll need.
Hetzner Cloud
You’ll require an account with Hetzner Cloud to make any progress. You can sign up yourself or use my referral link to get an initial account credit; totally up to you.
Once you’re in, you’ll need to procure an API token.
Creating an API token
Create a project in the Hetzner UI and give it a nice name, then go inside the project and navigate to the 🔑 Security page from the left-hand nav-bar. Go to the API tokens tab and then you’ll see the option to generate an API token.
Make sure your API token has read and write permissions. If you forgot to set that, you can edit the token to change it.
A domain name
While you’ll be able to work fine with pure IP addresses, this guide will work best if you have a domain handy, especially when it comes to setting up LetsEncrypt for SSL certificates. You don’t need to use the top-level of your domain, a subdomain will do just fine too.
Command line tools
Instructions will vary depending on your operating system, but you’ll need the following:
hetzner-k3s
requiredThis is a little program that will do the heavy lifting for us when creating a cluster.
kubectl
requiredWhile it’s also a dependency for hetzner-k3s, you can’t work with a K8S cluster without this.
helm
requiredHelm is a package manager for K8S and makes it easier to deploy pre-packaged software to the cluster. We’ll be using this a lot to avoid having to set up certain services by hand, as they tend to come with sensible defaults.
Bonus goodies
Lens
optionalLens is a desktop app that presents a comprehensive GUI for your K8S cluster. If you’re not sure where to start with the kubectl CLI then you might find this useful for exploration.
k9s
optionalI can recommend k9s if you prefer to stay in the terminal but would still prefer a more discoverable, visual UI over kubectl.