I keep running into the same issue trying to get microk8s running. The machine was completely wiped and is running Ubuntu 20.04… I also now have it directly connected to my University network so I am not proxying through other machines (i.e. my MAAS host).
Regardless of what I do, I am getting a CrashLookpBackOff error on the calico-kube-controllers-* service. I’m a bit stuck as at this point, as I haven’t really done anything “off script” yet… it’s a stock installation (although I did install nvidia-headless-510 for GPU drivers). I had this same error before even without installing drivers though, nor do I see that is the likely source of my problems.
The only slightly atypical thing on this machine is I have it also connected to a local network adapter, but I made sure my primary (and only) gateway is pointing to my University’s network…
Surprised that issues is popping up… I am trying to get kubeflow installed which isn’t apparently compatible yet with > 1.21…
It seems like the coredns service is up and running… but it says READY 0/1… Does that make sense? Also I tried to enable dashboard and am running into the same issue… I can’t tell if there are some weird firewall issues, but I disabled ufw at this point.
Network 1: 192.168.30.10
This adapter has the primary gateway, 192.168.30.1
– 192.168.30.1 is actually my MAAS head node…
Network 2: University IP address – Public
Of note, both networks have a gateway, but MAAS sets Network 1 as the default gateway.
— Network 1 as gateway didn’t work by default… proxy issues which I guessed would cause an issue.
Second scenario:
After installation, edited my netplan config, and made Network 2 (and my univesity subnet…) the default gateway. Oddly… this didn’t work (and I tried several times). However wget , curl, etc. work without any issues, so I do have network connectivity.
Current attempt:
Network 1 is set as default gateway (i.e. hops to my MAAS server)
BUT… before installation of microk8s, I made sure I updated my /etc/environment and set up http* proxies and no_proxy.
While that machine should have direct internet access, as a hail mary I modified my /etc/environment and set up the proxy config. The proxy address points to a MAAS headnode that I used to provision the machine initially…
