cluster-api-provider-hetzner VS terraform-hcloud-kube-hetzner

Hetzner Cloud is officially supported, but that means setting up VPSs in Hetzner's Cloud offering, whereas this project was intended as a more or less independent pure bare-metal cluster. I see they offer Bare Metal support as well, but I haven't dived too deep into it.

I haven't used KubeOne, but I have previously used Syself's https://github.com/syself/cluster-api-provider-hetzner which I believe works in a similar fashion. I think the approach is very interesting and plays right into the Kubernetes Operator playbook and its self-healing ambitions.

That being said, the complexity of the approach, probably in trying to span and resolve inconsistencies across such a wide landscape of providers, caused me quite a bit of grief. I eventually abandoned this approach after having some operator somewhere consistently attempt and fail to spin up a secondary control plane VPS against my wishes. After poring over loads of documentation and half a dozen CRDs in an attempt to resolve it, I threw in my hat.

Of course, Kubermatic is not Syself, and this was about a year ago, so it is entirely possible that both projects are absolutely superb solutions to the problem at this point.

For anyone interested in Kubernetes on Hetzner, there's a really interesting CAPI provider being actively developed:

https://github.com/syself/cluster-api-provider-hetzner

Just a hint running ML Workloads on Hetzner is pretty cheap! You could use for managing k8s: https://github.com/syself/cluster-api-provider-hetzner

we (Syself) release Cluster-API Provider Hetzner v1.0.0-beta.16.

ah okay they come from the upstream cluster-api project. The caph project implements only the infrastructure provider part of Cluster API.

you can easily use it with https://github.com/syself/cluster-api-provider-hetzner

I would use cluster-api-provider-hetzner from Syself.

Hetzner starting with https://github.com/kube-hetzner/terraform-hcloud-kube-hetzne..., plus registry using DigitalOcean.

However in the end my goto solution is k3s on hetzner cloud since it's got support for load balancers, ingress controllers with public IPS, persistent storage etc. It's cheaper than all the other cloud providers, although you need to run some code it doesn't have a 1 click solution. so I sold my hardware and used this https://github.com/kube-hetzner/terraform-hcloud-kube-hetzner. I run it when I need a kube cluster and kill it by deleting the project.

You can look at this: https://github.com/kube-hetzner/terraform-hcloud-kube-hetzner

This whole setup is around 70euros per month, and I can enjoy usenet and torrent downloads of Linux ISOs to constantly peak at 1Gbps speed. All of this is HA with Kubernetes using this.

OpenSUSE MicroOS, we use it here. Another good option would be Fedora CoreOS

It's not even close to major public cloud providers, but this is my setup:

* https://github.com/kube-hetzner/terraform-hcloud-kube-hetzne... (Terraform, Kubernetes bootstrap)

* Flux for CI

* nginx-ingress + Hetzner Loadbalancer (thanks to https://github.com/hetznercloud/hcloud-cloud-controller-mana...)

* Hetzner storage volumes (thanks to https://github.com/hetznercloud/csi-driver)

Kube-Hetzner supports Hetzner Cloud loadbalancers and volumes out of the box, though it also supports other components.

With Hetzner VMs and k3s one could run a k8 cluster with amazingly low cost. There are even ready-made repos that make it lighting fast to deploy and easy to maintain...

https://github.com/kube-hetzner/terraform-hcloud-kube-hetzne...

Even Hetzner maintains a few repos for that:

https://github.com/orgs/hetznercloud/repositories?q=kubernet...