Comment on page
Troubleshooting node events when node is not in ready status
🔍 Reason: Not enough disk space in the node
By default, the Kubernetes garbage collection (GC) gets triggered when the disk usage on a node crosses the HighThresholdPercent value (90% default). The ImageGCManager deletes images starting with the oldest and last used image until the disk usage reaches the LowThresholdPercent value. In some cases, GC does not get triggered. In such scenarios, the FreeDiskSpaceFailed event occurs.
Clean up some space or resize the volume. Look for unused docker images and clean up the unused images. Say, for instance, you can run the Spotify's GC to manually clean up the images on the node.
docker run --rm --privileged -v /var/run/docker.sock:/var/run/docker.sock -v /etc:/etc:ro spotify/docker-gc
🔍 Reason: Node is overloaded (not always reflected as disk or memory pressure). Not enough resources are allocated to Docker and it fails to respond in time.
- 1.Set limits for pods to prevent overloading the Nod
- 2.Cordon and evict the pods
- 3.Reboot the server
🔍 Reason 2: Evictions thresholds are too close to the node's physical memory limits
💡 Solution 2: Leave some buffer while setting eviction thresholds
🔍 Reason 1: invalid capacity 0 on image filesystem & the node is in 'NotReady' status
This occurs when kubelet does not recognize the disk availability.
💡 Solution 1: Restart containerd and kubelet daemons on the node.
systemctl restart containerd
systemctl restart kubelet
(or on microk8s)
sudo systemctl restart snap.microk8s.daemon-kubelet
sudo systemctl status snap.microk8s.daemon-kubelet
🔍 Reason 2: cgroups not enabled on the node(edge ARM)
💡 Solution 2: Enable cgroups and reboot the node
sudo echo "cgroup_enable=memory cgroup_memory=1" >> /boot/firmware/cmdline.txt