Node status is not ready (GITA-INC-005)

The Kubelet component from Kubernetes proactively checks nodes' available resources such as disk space, memory and PID count, in order to take action whenever any of these resources are running out, according to a measurement called eviction threshold.

In case the threshold is reached, the node is marked as being NotReady, whereby new Pods will not be accepted in the node, and current Pods may be terminated in an attempt to mitigate the issue. Network issues can also cause a node to become NotReady, be it from lack of connectivity or a misbehaving kube-proxy, since Kubernetes treats unreachable nodes as unhealthy.

For more information, visit the Kubernetes documentation