CloudProvider uninitialized:true with Hetzner CCM on K3S

[pomland-94]

Hey, I use the Hetzner CCM and CSI Driver, the csi driver doesn't come up, because of the Node Taint

Warning FailedScheduling 3m6s default-scheduler 0/1 nodes are available: 1 node(s) had taint {node.cloudprovider.kubernetes.io/uninitialized: true}, that the pod didn't tolerate. Warning FailedScheduling 113s default-scheduler 0/2 nodes are available: 2 node(s) had taint {node.cloudprovider.kubernetes.io/uninitialized: true}, that the pod didn't tolerate. Warning FailedScheduling 23s default-scheduler 0/4 nodes are available: 4 node(s) had taint {node.cloudprovider.kubernetes.io/uninitialized: true}, that the pod didn't tolerate.

That shows, that the Hetzner CCM doesn't change the Taints on the Nodes.

System: Debian 11 k3s version v1.22.7+k3s1 (8432d7f2) go version go1.16.10

And actual Hetzner CSI Driver and CCM-Networks Driver

[dnlsndr]

Seems like this would be an issue for the CCM repo not the CSI repo, doesn't it?

[github-actions[bot]]

This issue has been marked as stale because it has not had recent activity. The bot will close the issue if no further action occurs.