hetzner-k3s VS homelab

This is with the new version not yet released of my tool https://github.com/vitobotta/hetzner-k3s.

It uses k3s as Kubernetes flavor and Hetzner Cloud as provider. For this test I used extremely high concurrency so the tool hung twice of the process because I was hitting the Hetzner API too hard, so I had to interrupt it again and continue.

Excluding the time it paused/hubg due to the API, I calculated around 11 minutes total for the cluster creation. This includes:

- creating all the resources (cloud instances, firewall, load balancer for the Kubernetes API)

Try my project Hetzner-K3s, it’s by far the easiest and quickest way to create and manage clusters in Hetzner cloud. https://github.com/vitobotta/hetzner-k3s

Hi all, if you already use Kubernetes in any capacity or are you interested in it, would you mind spending a few minutes voting in a quick poll and hopefully answering a few questions? I would appreciate your help a ton because it would help me make the right decision and hopefully avoid a costly waste of time.

Everything is in a Github discussion at https://github.com/vitobotta/hetzner-k3s/discussions/296. A huge thank you in advance if you can help with this!

The new release introduces more customisation options for cluster/service CIDRs, cluster DNS, updated manifests for CSI/CCM/autoscaler, and a couple of improvement for creating large clusters. Check it out at https://github.com/vitobotta/hetzner-k3s

If you are already familiar with this tool, I'd love to know how it's worked for you so far. :)

https://github.com/vitobotta/hetzner-k3s

Kubernetes on Hetzner Cloud the easiest way

There’s this cool GitHub project that helps automate a lot of the process for K3s on Hetzner: https://github.com/vitobotta/hetzner-k3s

If you are willing to leave AWS in order to save a lot of money, you have an option in https://github.com/vitobotta/hetzner-k3s

At home in my Homelab I use PXE to provision bare metal nodes, and Ansible to deploy k8s on them. I know this setup isn't really used for anything yet, but I'm kinda proud of it. I can reprovision nodes at will by simply issuing one command, no monitor needed, no keyboard needed. That's the same level of comfort as a hypervisor, but it's bare metal.

This is my new repo for my homelab and it includes a k8s.yml file, which is much cleaner and uses more Ansible roles to keep various tasks separated. So you can easily break off k8s.yml and all the k8s roles into your own repo if you want to steal it. I'm not completely done with this setup though, I'm testing FluxCD right now because I might want to ditch ArgoCD.

I ended up writing my own, twice actually. Just re-wrote my entire k8s setup for my new homelab. It's published here on gitlab.com. It's not very well documented since it's for personal use but I think it emphasizes how easy it is to setup kubeadm and why there is little reason to make it more complicated than it needs to be.