Julian Tölle

After a quick glance at the involved code paths I have come to the conclusion that this will be hard to solve. We use `kubernetes/cloud-provider` to integrate with Kubernetes, and...

In Kubernetes 1.30 `k/cloud-provider` was updated to continually reconcile the node labels, so once we upgrade to that version everything should work as expected here. https://github.com/kubernetes/kubernetes/commit/0ab006b8a1e18b998e112b91fa5d7d868b577f68

Yes, setting the taint is the only way to get HCCM to update the labels. The commit I linked in my previous comment did not work out, the function that...

Now included in #671.

Sorry for the late response. --- Hey, I tried to reproduce the issue. The Hetzner Console indeed disables the "Attach Resource" button once there are multiple subnets and requires you...

Hey @abishekas, first off, there was an incident in our API yesterday around 17:00-17:40 CEST which might have been the cause for this. Can you try again today? If it...

The node does not have the unitialized taint that HCCM expects. Are you sure you started the kubelet on that node with `--cloud-provider=external`? HCCM will only "adopt" the node if...

Good to hear that everything works now. I am not really sure what the issue was, so I do not have any suggestions on what you can improve for the...

Do you have a commit/tag of cluster-autoscaler that was still working for you? You can enable debug logs for the Hetzner Cloud API calls by raising the verbosity to `5`:...

Without taking a look at the code: - I think the options should be the same as the subcommands: `hcloud load-balancer` -> `sort.load-balancer` - In the docs I would prefer...