empty kubeconfig about hetzner-k3s HOT 6 CLOSED

Hi, from the logs you can see that k3s is not starting at all on the masters so the cluster hasn't been initialised. It's probable that something in the post create commands is causing problems. You are making changes to the network configuration for example, what exactly are you changing there?

To see why k3s is not starting, you can ssh into the first master, and execute the command defined in /etc/systemd/system/k3s.* - you also need to source the .env file first. This will allow you to try and start k3s manually, so you can see if there are any errors.

from hetzner-k3s.

hi, thanks for help!
I'm trying to follow this: #252

from hetzner-k3s.

Have you tried what I suggested? :)

from hetzner-k3s.

Yes, it's working, thanks!

from hetzner-k3s.

What was the reason it was not starting?

from hetzner-k3s.

well, i'm using ssh agent forwarding and I have several keys loaded.
But hetzner's debian 12 somehow does not allow these keys, so after I disabled agent forwarding on my side (not in cluster.yaml) it's started to working. wierd.

i got this message when I used ssh-agent forward: Received disconnect from 10.0.9.4 port 22:2: Too many authentication failures

from hetzner-k3s.