Description
Summary
Watching microk8s kubectl get all --all-namespaces
shows services including hostpath-provisioner, dashboard, and dns getting into CrashLoopBackOff states repeatedly. hostpath-provisioner usually seems like the first to fail. As per the troubleshooting guide I have run these commands:
sudo ufw allow in on vxlan.calico && sudo ufw allow out on vxlan.calico
sudo ufw allow in on cali+ && sudo ufw allow out on cali+
And rebooted, but the issue does not go away.
What Should Happen Instead?
microk8s kubectl get all --all-namespaces
should eventually show all pods in the "Running" status with "READY" being "1/1".
Reproduction Steps
- Turn on my computer
watch microk8s kubectl get all --all-namespaces
- Various system pods start erroring and getting into CrashLoopBackOff status
For additional context, I am just trying to set up microk8s for the first time on a home server with a fresh install of Ubuntu server 20.04 LTS. The one thing I think might be problem-causing is that I have the partition I'm running in formatted to only 15 GB.
Introspection Report
inspection-report-20230105_063544.tar.gz
Are you interested in contributing with a fix?
No. I don't know what's going on sorry.