Open klauserber opened 1 year ago
Is there any update on this issue or was someone able to resolve it?
Realizing I'm poking an old issue here, but do you remember what version of Rancher you used, @klauserber ? Still having the same issue using a local Rancher 2.7 instance provisioned with Hetzner Cloud credentials and with all the known fixes applied.
Also, if you used Rancher 2.6+ as well, where do you set the instance type in the new UI?
Try to enable the userDataFromFile flag in the settings by the pool. Otherwise the cloud-init file by rancher will not be copied/executed on the node.
Also poking this issue. Have the same issue waiting for agent. Tried a lot of combinations RKE2/K3S different networks etc. My rancher currently runs on a single node K3S install.
Try to pass https://github.com/hetznercloud/hcloud-cloud-controller-manager/releases/download/v1.20.0/ccm-networks.yaml in the Add On Config -> Additional Manifest.
I added the api key and network hardcoded in the yaml.
And use CLoud Provider: External and --cloud-provider=external as Additional Kubelet Args, Additional Controller Manager Args and Additional API Server Args.
Also add the Private IPS in TLS Names.
I have problems to create RKE2 or K3S clusters. RKE clusters are working fine.
Test scenario:
Test results:
Provisioning log:
Log Rancher pod: