Can't get status, inspect stuck

microk8s status doesn’t show anything. It says, microk8s isn’t running. I stopped and started microk8s but it didn’t work. And, I can’t run microk8s inspect either.

(base) user01@user-X299-WU8:/var/snap/microk8s/current/args$ microk8s status
microk8s is not running. Use microk8s inspect for a deeper inspection.
(base) user01@user-X299-WU8:/var/snap/microk8s/current/args$ microk8s stop
Stopped.
(base) user01@user-X299-WU8:/var/snap/microk8s/current/args$ microk8s start
Started.
(base) user01@user-X299-WU8:/var/snap/microk8s/current/args$ microk8s status
microk8s is not running. Use microk8s inspect for a deeper inspection.

(base) user01@user-X299-WU8:/var/snap/microk8s/current/args$ microk8s inspect
Inspecting Certificates
Inspecting services
  Service snap.microk8s.daemon-cluster-agent is running
  Service snap.microk8s.daemon-containerd is running
  Service snap.microk8s.daemon-apiserver is running
  Service snap.microk8s.daemon-apiserver-kicker is running
  Service snap.microk8s.daemon-control-plane-kicker is running
  Service snap.microk8s.daemon-proxy is running
  Service snap.microk8s.daemon-kubelet is running
  Service snap.microk8s.daemon-scheduler is running
  Service snap.microk8s.daemon-controller-manager is running
  Copy service arguments to the final report tarball
Inspecting AppArmor configuration
Gathering system information
  Copy processes list to the final report tarball
  Copy snap list to the final report tarball
  Copy VM name (or none) to the final report tarball
  Copy disk usage information to the final report tarball
  Copy memory usage information to the final report tarball
  Copy server uptime to the final report tarball
  Copy current linux distribution to the final report tarball
  Copy openSSL information to the final report tarball
  Copy network configuration to the final report tarball
Inspecting kubernetes cluster
  Inspect kubernetes cluster
Inspecting juju
  Inspect Juju

It stucks more than 10 minutes.

[RaghuMeda]

I have run into something similar and I get inconsistent results…

Basically, a low powered (1 cpu 1 gb ram) Azure VM with ubuntu server 20 lts never returns a value for microk8s status or microk8s inspect… and instead hangs.

Is that behavior expected?

It’s the same issue for me. I am using Raspberry Pi3 with 2 cpu and 1 GB ram and microk8s status and microk8s inspect always hangs out. Its pure luck when it works. I did replicate the same issue happens in AWS EC2 with 2 cpu and 1 GB ARM64 system. I beleieve Microk8s is not tested throughly yet for ARM64 systems with low power. Although it says it works for low power devices thats not true.

[balchua]

@betsegaw my guess is that the kernel is killing the apiserver due to memory pressure. You may want to try enabling swap. But that is highly discouraged by kubernetes. Imho 1GB is too small for kubernetes.