Found the issue: The k3s instance I was running was not matching the image I was using in my cluster configuration (v1.31.5-k3s1 VS v1.20.4-k3s1) Hi, I'm having some trouble trying to create a cluster, the command hangs. I'm using

k3d version v5.8.3
k3s version v1.31.5-k3s1 (default)

Below configuration

apiVersion: k3d.io/v1alpha5
kind: Simple
image: rancher/k3s:v1.20.4-k3s1
metadata:
  name: dev
servers: 1
agents: 1

produces the following output (and it never exits):

INFO[0000] Using config file test.yaml (k3d.io/v1alpha5#simple) 
INFO[0000] Prep: Network                                
INFO[0000] Created network 'k3d-dev'                    
INFO[0000] Created image volume k3d-dev-images          
INFO[0000] Starting new tools node...                   
INFO[0000] Starting node 'k3d-dev-tools'                
INFO[0001] Creating node 'k3d-dev-server-0'             
INFO[0001] Creating node 'k3d-dev-agent-0'              
INFO[0001] Creating LoadBalancer 'k3d-dev-serverlb'     
INFO[0001] Using the k3d-tools node to gather environment information 
INFO[0001] HostIP: using network gateway 172.18.0.1 address 
INFO[0001] Starting cluster 'dev'                       
INFO[0001] Starting servers...                          
INFO[0001] Starting node 'k3d-dev-server-0'             
INFO[0005] Starting agents...                           
INFO[0005] Starting node 'k3d-dev-agent-0'

Inside the server container, the relevant log line is

The connection to the server 127.0.0.1:6443 was refused - did you specify the right host or port?

And similarly, the agent has the following log line

The connection to the server localhost:8080 was refused - did you specify the right host or port?

I was under the impression that I didn't need to specify everything in the configuration, and some defaults would fill the bank. Is that wrong? Note that the issue doesn't occur if I remove the agent from the configuration.