Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kubectl and microk8s unresponsive, and unable to reset #4824

Open
aristotelos opened this issue Jan 15, 2025 · 0 comments
Open

Kubectl and microk8s unresponsive, and unable to reset #4824

aristotelos opened this issue Jan 15, 2025 · 0 comments

Comments

@aristotelos
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant