Kubectl and microk8s unresponsive, and unable to reset

[aristotelos]

Summary

Microk8s suddenly turned completely unresponsive, and there is no way to reset it. I am using microk8s installed on WSL (Windows Subsystem for Linux) with just one node.

microk8s kubectl get services fails with Unable to connect to the server: net/http: TLS handshake timeout
microk8s status returns microk8s is not running. Use microk8s inspect for a deeper inspection.
sudo microk8s reset exits with Failed to query the cluster nodes.

I tried microk8s stop followed by microk8s start which do not report errors, but do also not repair the system.

What Should Happen Instead?

At least microk8s reset should work.

Reproduction Steps

I do not know how to reproduce it, it just suddenly happened.

Introspection Report

inspection-report-20250115_074332.tar.gz

Can you suggest a fix?

microk8s reset should reset itself if microk8s is running on a single node.

Are you interested in contributing with a fix?

no

[imkonsowa]

I remember having a such problem and it was a ~/.kube/config file issue, try microk8s config > ~/.kubec/config to override existing config file.

[bschimke95]

Hi @aristotelos

I assume your network configuration changed. In that case, microk8s will re-issue the certificates and your kube-config will become outdated. Recreating the config as @imkonsowa describes, should fix the connection problem.

[abhibhaw]

This didn't work, any other solution?