-
Notifications
You must be signed in to change notification settings - Fork 777
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
Microk8s stuck and cannot connect to VM on MacOS #4456
Comments
@aaronpliu would you be able to share an inspection report tarball so we have a look at the logs ( |
microk8s inspect |
Warning: the "--mem" long option is deprecated in favour of "--memory". Please update any scripts, etc. |
Firewall is disabled. Let me know if additional info is needed. |
I had this issue with channel 1.26 installed, and was able to solve it by upgrading MicroK8s to a later version
(still getting Have used this guide to choose a stable channel: |
Summary
I installed Microk8s latest version on MacOS M2. it was working fine after installation, but weird behavior appeared after it running for a couple of days that whatever type multipass command or microk8s kubectl command to access, it's very slow or no response. Even if I use k9s to access, it lost all of connection info. Firstly, I doubt it's due to Apple M2 issue, then switch to Apple Intel, it's still same issue.
I really would like to install an available k8s cluster in MacOS. However, microk8s cannot be running with stable status. Actually, I did not install any other image there (Only enable required plugins, like registry, dns, dashboard, istio...etc).
Btw, I stopped microk8s instance and restart a new one, the IP address changed, and microk8s is OK to access again (it still repeat the same behavior, become slow -> not access -> no response for kubectl command -> down)
The text was updated successfully, but these errors were encountered: