I can’t get microk8s 1.19.2 to start on RHEL 7.8, using snap. Same works fine on another machine running 7.7.
Lots of errors like:
Nov 10 04:50:25 177 microk8s.daemon-kubelet: E1110 04:50:25.789334 9288 pod_workers.go:191] Error syncing pod cb666780-24cd-4a40-bf17-9c9245204acc (“hostpath-provisioner-5c65fbdb4f-gvrfn_kube-system(cb666780-24cd-4a40-bf17-9c9245204acc)”), skipping: failed to ensure that the pod: cb666780-24cd-4a40-bf17-9c9245204acc cgroups exist and are correctly applied: failed to create container for [kubepods besteffort podcb666780-24cd-4a40-bf17-9c9245204acc] : mkdir /sys/fs/cgroup/memory/kubepods/besteffort/podcb666780-24cd-4a40-bf17-9c9245204acc: cannot allocate memory
The pods are stuck in ContainerCreating. Both machines (v7.7 and v7.8) were running clustered with microk8s 1.19.0 for several month without any problem, then I made some configuration changes to the workload (not microk8s) and couldn’t bring the cluster back up, ended up doing a fresh install of 1.19.2.
How do I diagnose this further?
Kubernetes version: microk8s 1.19.2
Cloud being used: bare-metal
Installation method: snap
Host OS: RHEL 7.8
CNI and version:
CRI and version:
You can format your yaml by highlighting it and pressing Ctrl-Shift-C, it will make your output easier to read.