microK8s stalls on OCI E2.1.Micro instance

Details of the instance are here under Compute. It’s a 1 gb ram instance with 40 gigs of attached storage, which according to the issues I’ve read here, should fall within minimum system reqs.

1.19 never moves past the configure hook step when installing. 1.18, 1.18 refreshed to 1.19, 1.17, and 1.16 stall given a microk8s status or microk8s inspect command 90% of the time. I was able to get one inspect tarball out of this, which I’ve attached.

If anyone else wants to give this a try, Oracle Cloud offers no-catch always free compute resources. You can use their Terraform example here together with the relevant Terraform provider docs.

I’d love to receive an answer on either A. what the official minimum system requirements of microK8s are or B. what I can do to get a functional installation. It doesn’t need more than dns and storage enabled (for the purposes of testing, I never enabled these).

inspection-report-20201027_170633.tar.gz

[worldofgeese]

I see in the issue linked to do the following for Oracle Cloud Infrastructure deployments:

sudo iptabled -D  INPUT -j REJECT --reject-with icmp-host-prohibited
sudo iptabled -D  FORWARD -j REJECT --reject-with icmp-host-prohibited

I needed to change the two instances of iptabled to iptables

sudo iptables -D  INPUT -j REJECT --reject-with icmp-host-prohibited
sudo iptables -D  FORWARD -j REJECT --reject-with icmp-host-prohibited

after which microk8s status reports microk8s is running!

Thank you @ktsakalozos for sticking with me through this one! 🙇

[worldofgeese]

Imho 1Gb for kubernetes is too small.

K3s occupies this same space of small and lean k8s distros and does fine on a 1Gb vps.

For what it’s worth I have microK8s running two deployments on a 2 gig AWS vps no problem.

But if it is the case that microK8s requires 2 gig minimum, I’d like to see a direct response from the team at Canonical updating the minimums.