Hi. I am trying to setup a simple two-node bare metal cluster with k3s on Hetzner dedicated servers and I am having some connectivity issues. The servers are running 22.04 LTS with ufw disabled. The hetzner firewall is set to only allow SSH through to the public IPs, but a "vSwitch" has been setup providing a VLAN, where one server is 10.0.0.1 and the other is 10.0.0.2. The cluster will for now only run CI/CD agents that don't need ingress, so I don't really want to expose anything on public IPs. The two servers can succesfully ping and ssh each other via the 10.0.0.x IPs. I am setting up 10.0.0.1 as the master and that operation is seemingly succesful. The k3s kubectl cluster-info reports: Kubernetes control plane is running at https://127.0.0.1:6443 CoreDNS is running at https://127.0.0.1:6443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy Metrics-server is running at https://127.0.0.1:6443/api/v1/namespaces/kube-system/services/https:metrics-server:https/proxy However, when I try to add 10.0.0.2 as a node, the operation hangs on: [INFO] systemd: Starting k3s-agent