You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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 withUnable to connect to the server: net/http: TLS handshake timeout
microk8s status
returnsmicrok8s is not running. Use microk8s inspect for a deeper inspection.
sudo microk8s reset
exits withFailed to query the cluster nodes.
I tried
microk8s stop
followed bymicrok8s 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
The text was updated successfully, but these errors were encountered: