kronform VS hcloud-cloud-controller-manager

https://datavirke.dk/posts/bare-metal-kubernetes-first-incid...

Source code repository (set up in Part III) for node configuration and deployed services is available at https://github.com/MathiasPius/kronform

While the documentation was initially intended more as a future reference for myself as well as a log of decisions made, and why I made them, I've received some really good feedback and ideas already, and figured it might be interesting to the hacker community :)

When it comes to load balancing, I think the hcloud-cloud-controller-manager[1] is probably your best bet, and although I haven't tested it, I'm sure it can be coerced into some kind of working configuration with the vSwitch/Cloud Network coupling, even none of cluster is actually Cloud-based.

I haven't used Sidero Omni yet, but if it's as well architected as Talos is, I'm sure it's an excellent solution. It still leaves open the question of ordering and provisioning the servers themselves. For simpler use-cases it wouldn't be too difficult to hack together a script to interact with the Hetzner Robot API to achieve this goal, but if I wanted any level of robustness, and if you'll excuse the shameless plug, I think I'd write a custom operator in Rust using my hrobot-rs[2] library :)

[1] https://github.com/hetznercloud/hcloud-cloud-controller-mana...

Did you actually use the Hetzner LBs or did you just send traffic to the NodePort?

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.

I plan to do the same or have already implemented it. I use the Hetzner private networks with the hcloud-cloud-controller-manager https://github.com/hetznercloud/hcloud-cloud-controller-manager. This creates routes so that the nodes are also connected to each other in the private network. All kubernetes resources listen on the private network. Except for the Kubernetes API, which listens on the external IP of the master so I can use kubectl from home. The actual gateway into the cluster is controlled by a load balancer from Hetzner.

I want to use Hetzner's Load Balancer as a Nginx Ingress controller. I follow this suggestion to install Nginx Ingress via helm.