Closed knkski closed 4 years ago
Update on this, trying out regular kubectl
with microk8s.config
fails:
$ microk8s.config > kubeconfig
$ kubectl --kubeconfig=kubeconfig get pods --all-namespaces
Unable to connect to the server: x509: certificate is valid for 127.0.0.1, 10.152.183.1, 172.16.213.53, 192.168.122.1, 10.185.200.1, 172.26.0.1, 10.1.1.1, 10.36.117.1, not 192.168.1.158
One more update, after switching to another new wireless network, this started working for me again. Juju bootstraps just fine, and kubectl --kubeconfig=kubeconfig get pods --all-namespaces
is able to properly talk to the microk8s API.
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.
Migrating from https://bugs.launchpad.net/juju/+bug/1830219, as it's suspected to not be a juju issue.
I have been bouncing between various networks the last few days, and that seems to have caused an issue where I would attempt to run
juju bootstrap microk8s uk8s
, and would get this output:Doing
microk8s.reset
didn't fix the issue, nor did removing all clouds and controllers from Juju. Reinstalling the microk8s snap fixed the issue.Here's some debug output from when it happened: