hcloud-cloud-controller-manager VS cli

export KUBECONFIG=hetzner-cluster-kubeconfig.yaml # Install Hetzner CCM kubectl apply -f https://github.com/hetznercloud/hcloud-cloud-controller-manager/releases/latest/download/ccm.yaml # Install Flannel CNI - You can use your preferred CNI instead, e.g. Cilium kubectl apply -f https://github.com/flannel-io/flannel/releases/latest/download/kube-flannel.yml

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.

hopefully i am doing everything right and that is the right location and the right way to post this. it is my first post here on HN. being a long time reader of HN i thought maybe it is the right location to ask other developers to vote for a unified cli/terraform experience with hetzner.

hetzner brought me to terraform as they mentioned it in their documentation, newsletter or blog (i cannot remember). since then, i always preferred providers which had a good api or even better a good api and a terraform provider.

while working with terraform/opentofu to interact with hetzner i also use their cli tool to quickly create json/yaml lists of resources to import or interact with them. sadly the official terraform provider and the cli tool only supports their cloud product. i really miss that it also supports the new s3 object storage, their dns and their share product. in the end i miss that the tool supports all their products and provides a unified way to interact with hetzner via cli and/or terraform.

the hcloud tool developers understandably say they only support the cloud api with their tool. in my opinion they really have done am awesome job with the hcloud tool. i hope we can get some traction and shovel some budget to them by creating support requests which ask for support of their other products which maybe lead to a support of all their product.

if you feel the same way, you can help: if you already have an account with some servers in it (paying customer), just login to your account and open a support ticket with the text "We vote for https://github.com/hetznercloud/cli/issues/918"