Microk8s.status not running; microk8s.inspect looks good

I have a new install of Ubuntu on a Raspberry Pi 4. I used snap to install microk8s.

microk8s.status says the cluster is not running
microk8s.inspect shows all the services running
kubectl get nodes shows one node, not ready

Before installing I didn’t enable cgroups memory, so I did that and then rebooted, but that made no difference.

Are there other steps required to get this running? Unlike with kubeadm installs I didn’t manually disable swap, is that necessary?

Are there steps I can/should take to troubleshoot? What am I looking for in terms of likely reasons the cluster wouldn’t start up?

Cluster information:

Kubernetes version: 1.16.3
Cloud being used: bare-metal
Installation method: snap
Host OS: Ubuntu
CNI and version:
CRI and version:

What’s interesting to me, is that I can install add-ons (like dns/dashboard) and the pods appear. They never leave a Pending state, but some parts of the cluster are obviously working to actually set up the pods.

Facing exact same issue here on RPI4.
Kubernetes version: 1.17
Installation method: snap
Hardware: Raspberry Pi 4
Host OS: Ubuntu 19.10 (rpi4 image)

For anyone looking for an answer, needed to enable cgroups for memory in rpi4 setup:

sudo emacs /boot/firmware/nobtcmd.txt

And add:

cgroup_enable=memory cgroup_memory=1

After rebooting should see ‘1’:

grep mem /proc/cgroups | awk '{ print $4 }'
1
1 Like