Cannot schedule PODs: NodeHasDiskPressure about microk8s HOT 5 CLOSED

Hi @edsiper ,

In microk8s your machine is also the node kubernetes is using. Disk pressure means you do not have enough resources for kubernetes to schedule pods. You can either free disk space by deleting files, or set the pod eviction limits as described in [1].

To set the pod eviction limits you have to set the --eviction-hard and --eviction-minimum-reclaim parameters in kubelet. The arguments used to start the daemons microk8s ships are under /var/snap/microk8s/current/args/. I suggest you append the following line in /var/snap/microk8s/current/args/kubelet

 --eviction-hard="memory.available<500Mi,nodefs.available<1Gi,imagefs.available<1Gi"

And then you will need to restart kubelet: sudo systemctl restart snap.microk8s.daemon-kubelet

You bring forward a valid point, the default eviction limits make sense for a server setup but may be to conservative for a standalone dev environment. We should set sensible defaults here: https://github.com/juju-solutions/microk8s/blob/master/microk8s-resources/default-args/kubelet

Thanks

[1] https://kubernetes.io/docs/tasks/administer-cluster/out-of-resource/

from microk8s.

that fixed the issue!, thanks for your help.

I'd suggest those values comes by default...

from microk8s.

I agree, I'll open a pull request to start that process

from microk8s.

Works here @ktsakalozos. I was going through the same issue.

from microk8s.

Can't those arguments be passed by kubectl or API ?

from microk8s.