-
Notifications
You must be signed in to change notification settings - Fork 948
Open
Description
Hello,
It works with 1.34, but when running with 1.35 it's stuck at
TASK [k3s.orchestration.k3s_agent : Enable and check K3s agent service] *****************************************************
One of the worker's node status
node4 | FAILED | rc=3 >>
● k3s-agent.service - Lightweight Kubernetes
Loaded: loaded (/etc/systemd/system/k3s-agent.service; enabled; vendor preset: enabled)
Active: activating (start) since Sat 2026-02-28 15:49:37 UTC; 15min ago
Docs: https://k3s.io
Process: 290433 ExecStartPre=/sbin/modprobe br_netfilter (code=exited, status=0/SUCCESS)
Process: 290434 ExecStartPre=/sbin/modprobe overlay (code=exited, status=0/SUCCESS)
Main PID: 290435 (k3s-agent)
Tasks: 13
Memory: 260.2M
CGroup: /system.slice/k3s-agent.service
└─290435 "/usr/local/bin/k3s agent" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ""
Feb 28 16:03:28 node4 k3s[290435]: time="2026-02-28T16:03:28Z" level=info msg="Waiting to retrieve agent configuration; server is not ready: failed to get CA certs: Get \"https://127.0.0.1:6444/cacerts\": EOF"
Feb 28 16:03:38 node4 k3s[290435]: time="2026-02-28T16:03:38Z" level=info msg="Waiting to retrieve agent configuration; server is not ready: /var/lib/rancher/k3s/agent/serving-kubelet.crt: https://127.0.0.1:6444/v1-k3s/serving-kubelet.crt: 503 Service Unavailable"
Feb 28 16:03:48 node4 k3s[290435]: time="2026-02-28T16:03:48Z" level=info msg="Waiting to retrieve agent configuration; server is not ready: failed to get CA certs: Get \"https://127.0.0.1:6444/cacerts\": EOF"
Feb 28 16:03:57 node4 k3s[290435]: time="2026-02-28T16:03:57Z" level=info msg="Waiting to retrieve agent configuration; server is not ready: failed to get CA certs: Get \"https://127.0.0.1:6444/cacerts\": EOF"
Feb 28 16:04:06 node4 k3s[290435]: time="2026-02-28T16:04:06Z" level=info msg="Waiting to retrieve agent configuration; server is not ready: /var/lib/rancher/k3s/agent/serving-kubelet.crt: https://127.0.0.1:6444/v1-k3s/serving-kubelet.crt: 503 Service Unavailable"
Feb 28 16:04:15 node4 k3s[290435]: time="2026-02-28T16:04:15Z" level=info msg="Waiting to retrieve agent configuration; server is not ready: failed to get CA certs: Get \"https://127.0.0.1:6444/cacerts\": EOF"
Feb 28 16:04:23 node4 k3s[290435]: time="2026-02-28T16:04:23Z" level=info msg="Waiting to retrieve agent configuration; server is not ready: failed to get CA certs: Get \"https://127.0.0.1:6444/cacerts\": EOF"
Feb 28 16:04:32 node4 k3s[290435]: time="2026-02-28T16:04:32Z" level=info msg="Waiting to retrieve agent configuration; server is not ready: /var/lib/rancher/k3s/agent/serving-kubelet.crt: https://127.0.0.1:6444/v1-k3s/serving-kubelet.crt: 503 Service Unavailable"
Feb 28 16:04:41 node4 k3s[290435]: time="2026-02-28T16:04:41Z" level=info msg="Waiting to retrieve agent configuration; server is not ready: failed to get CA certs: Get \"https://127.0.0.1:6444/cacerts\": EOF"
Feb 28 16:04:48 node4 k3s[290435]: time="2026-02-28T16:04:48Z" level=info msg="Waiting to retrieve agent configuration; server is not ready: /var/lib/rancher/k3s/agent/serving-kubelet.crt: https://127.0.0.1:6444/v1-k3s/serving-kubelet.crt: 503 Service Unavailable"non-zero return code
I'll be sticking to v1.34.3+k3s1 meanwhile, no hurry for me.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels