-
Notifications
You must be signed in to change notification settings - Fork 776
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
Can't get status, inspect stuck #2125
Comments
@kwonmha just wanted to check if you are still facing this issue. Thanks |
I can't reproduce this issue now. |
Great to hear that. Thanks 👍 |
something is off, my cluster is not working at all, tried re installing all the nodes but it keeps happening, here is my tarball: |
@Pezhvak can you try to remove it with |
I have run into something similar and I get inconsistent results... Basically, a low powered (1 cpu 1 gb ram) Azure VM with ubuntu server 20 lts never returns a value for microk8s status or microk8s inspect... and instead hangs. Is that behavior expected? |
@betsegaw my guess is that the kernel is killing the apiserver due to memory pressure. You may want to try enabling swap. But that is highly discouraged by kubernetes. Imho 1GB is too small for kubernetes. |
@balchua - thank you for the reply and you are correct, increasing the memory of the VM fixed things. Sorry for the late confirmation but I had my github notifications off and didn't see someone had replied. |
It's the same issue for me. I am using Raspberry Pi3 with 2 cpu and 1 GB ram and microk8s status and microk8s inspect always hangs out. Its pure luck when it works. I did replicate the same issue happens in AWS EC2 with 2 cpu and 1 GB ARM64 system. I beleieve Microk8s is not tested throughly yet for ARM64 systems with low power. Although it says it works for low power devices thats not true. |
have same issue from 1.23/stable with Raspberry Pi3. Is there specific version that works with rpi3? or any plan to fix issue?
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I'm having the same issue after rebooting my Mac m1 over Multipass. |
I'm having similar issues on an RPi 5 8GB, after my internal network's ip changed. I'm in the process of trying to get it all working again but it just hangs:
|
I had a similar problem. What worked for me: microk8s stop
microk8s refresh-certs --check
The CA certificate will expire in X days.
The server certificate will expire in X days.
The front proxy client certificate will expire in X days.
microk8s refresh-certs --cert server.crt
microk8s start |
Having the same issue here on an Pi3 as well, anyone found a fix yet? |
microk8s status
doesn't show anything.It says, microk8s isn't running.
I stopped and started microk8s but it didn't work.
And, I can't run
microk8s inspect
either.It stucks more than 10 minutes.
The text was updated successfully, but these errors were encountered: