cluster-api-provider-hetzner

Would CAPH solve your issue? https://github.com/syself/cluster-api-provider-hetzner you would wire up cluster autoscaler to point to it using clusterapi https://github.com/kubernetes/autoscaler/tree/a9cb59fdd2dd88...

Ive also been using Cluster-API + Cluster-API-Provider-Hetzner https://github.com/syself/cluster-api-provider-hetzner works rock solid

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

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

> Do you have Kubernetes clusters in Hetzner already? If yes, which tool did you use to create them? Would be interested to know more about alternatives people are using. Yes. I use ClusterAPI[1] with the cluster-api-provider-hetzner[2] & Talos[3] (and Talos' cluster-api components) for that. [1]: https://cluster-api.sigs.k8s.io/user/quick-start.html [2]: https://github.com/syself/cluster-api-provider-hetzner [3]: https://talos.dev