This message was deleted.

Did you try

k3d cluster stop/start

already?

no, other partner restarted the host, i didn't stop the cluster

Yeah but that results in an uncontrolled restart. It usually works, but seems like in your case it broke something, so doing a controlled restart using k3d commands may help.

so, what remedial measures can I take?

Did you try

k3d cluster stop/start

already?

If you did that, it would be nice to have the logs of the server and agent node containers (docker logs)

yeah, i did it. and i found the command start always stay in start state. and agent logs are

Waiting to retrieve agent configuration; server is not ready: failed to retrieve configuration from server: <https://127.0.0.1:6444/v1-k3s/config>: 401 Unauthorized

What about the server logs?

it has too many logs, but all of them almost are logs from application pods

Could it be, that there's another service taking the requests that should go to the K3s server? Can you still list pods,. etc. via kubectl?