Open boris-savic opened 4 days ago
If i remove the node.cloudprovider.kubernetes.io/uninitialized
taint manually the creation is completed, but i seem to end up with non functional nodes...
The nodes are missing external IPs in K3s on them and topology labels. Nodes on the Hetzner console have public IPs, I can SSH to them, but when I rerun the hetzner-k3s create command, the process is stuck on SSH step Waiting for successful ssh connectivity with instance
Hi,
I've stumbled on another issue, that I cannot seem to find any existing issues related to.
So I've setup my cluster with two worker pools, and tried to add another ARM based workers into the mix. Nodes get created, I can ssh to them, but they never become active on the k3s. The create command gets stuck on Starting k3s-agent. Below is my config file and all the logs.
I have tried with non-arm instance, but same behavior, so it's not related to the ARM.
Using hetzner-k3s version 2.0.8 on OSX.
My config is following:
Logs on the workers that are stuck:
Journal logs