cluster-api-provider-hetzner VS addon-controller

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.

👏 Support this project Every contribution counts! If you enjoyed this article, check out the Projectsveltos GitHub repo. You can star 🌟 the project if you find it helpful.

Sveltos is an open-source Kubernetes project to deploy add-ons in a multitude of Kubernetes cluster. Sveltos can also be instructed to watch for changes in ConfigMaps and Secrets and triggers rolling upgrades for the associated resources, ensuring that applications stay up-to-date.

If you enjoyed this article, please check out the GitHub repo for the project. You can also star 🌟 the project if you found it helpful. The GitHub repo is a great resource for getting started with the project. It contains the code, documentation, and examples. You can also find the latest news and updates on the project on the GitHub repo. Thank you for reading!

And if you like it, please star ⭐ the project on GitHub

With projectsveltos, you can instruct add-on controller to deploy resources using Kustomize (on top of Helm charts and regular YAMLs). Then you could use its event-driven framework to deploy extra resources on demands.

When deploying add-ons with Sveltos Kuberntes add-on controller it is now possible to also enforce add-on constraints (defined in the management cluster using openapi).

Open a bug/feature enhancement on github

Here for instance https://github.com/projectsveltos/sveltos-manager/blob/main/.github/workflows/main.yaml

Documentation can be found here