-
Notifications
You must be signed in to change notification settings - Fork 756
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
Unable To Interact With Microk8s on Windows 2022 With Virtual Box #4476
Comments
Found a similar issue from some time ago. If the IP of the master node changed, how would I know? Where would I find the new IP? |
Hi @ThePieMonster, you should either ensure that the VM has the same IP address across reboots (see linked issue for some steps), or simply see the current IP (by means of |
@neoaggelos The host machine that is running MicroK8S is a physical windows server machine with a static IP. |
Ah, okay, this could probably be a different kind of issue than the one you linked. I am seeing this in the logs of
Can you try to create this directory manually? Running something along those lines on the VM should help:
Then, observe the logs to see if k8s-dqlite is coming up with:
|
I ended up switching to MiniKube as it runs in the context of Docker or Hyper-V without issue. |
Summary
Unable to interact wth microk8s
microk8s kubectl get pods
E0331 18:54:13.759087 3084 memcache.go:265] couldn't get current server API group list: Get "https://10.0.2.15:16443/api?timeout=32s": dial tcp 10.0.2.15:16443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
What Should Happen Instead?
kubectl command provides information
Reproduction Steps
Install microk8s with Oracle Virtual Box on Windows Server 2022 and try to interact with the cluster.
Introspection Report
inspection-report-20240331_185644.tar.gz
The text was updated successfully, but these errors were encountered: