Closed xinity closed 5 months ago
I can reproduce the problem on AKS cluster:
Readiness: tcp-socket 127.0.0.1:6443 delay=60s timeout=10s period=10s #success=1 #failure=5
However I can see k3s is up and running normally:
/ # kubectl get nodes
NAME STATUS ROLES AGE VERSION
demo-k3k-server-0 Ready control-plane,etcd,master 9m21s v1.26.1+k3s1
# netstat -tlnu
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 127.0.0.1:10257 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:10256 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:10259 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:10258 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:10249 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:10248 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:2379 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:2381 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:2380 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:6444 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:10010 0.0.0.0:* LISTEN
tcp 0 0 10.244.2.4:2379 0.0.0.0:* LISTEN
tcp 0 0 10.244.2.4:2380 0.0.0.0:* LISTEN
tcp 0 0 :::10250 :::* LISTEN
tcp 0 0 :::6443 :::* LISTEN
Tested and worked on AKS cluster k3k version: v0.2.1 chart-0.1.4-r1
i've been trying k3k on my AKS cluster:
tried this yaml :
the deployment fails because the readiness probe fails ( 127.0.0.1:6443 connection refused)
full log available here: https://pastebin.com/me8fhV8q
any hints on what's happening perhaps ? :)