vitobotta
commented
2 months ago It seems the problem was that in v2 I changed the logic to create an instance so that I power it on and attach it to the private network in separate steps with a little delay in between. This was done to avoid some issues that can occur when creating a large cluster from the get go with a private network or when adding many notes at once and a private network is in use.
In your case, you had disabled the public IPs, so when the instance was created was left without IPs and therefore everything got stuck. Since it's unlikely that someone might create large clusters from the get go (I only did this in my tests for benchmarks) I have reverted the change mentioned above, so the instance gets attached to the network automatically again and always has an IP (private only in this case) and the setup can continue.
I have pushed these changes and it's currently building rc4. Monitor https://github.com/vitobotta/hetzner-k3s/actions/runs/10356376895 and try with the binary as soon as the one for your OS is ready. Please let me know how it goes :)
Extracted from https://github.com/vitobotta/hetzner-k3s/discussions/385#discussioncomment-10168998
Scenario: existing private network only, no public IP addresses:
I had to manually assign the master server to the existing network (while the tool, version 2.0.0rc2, waited for instance to be up in a loop). It then completed.
My config:
and some log output: