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
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:
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: