Hello @colinjohnriddell ,
NotReady status on a node can be caused due to multiple reasons::
- The node kubelet service has stopped running.
- The container runtime(Docker) has stopped running.
- The node VM is no longer available.
- Resource contention on the Nodes.
It is a best practice that Kubernetes nodes should be treated as ephemeral. Because of this, it is common to recycle a node that has an issue to replace it with a healthy node. This can fix many common problems specific to nodes. Generally, we see Node in Not Ready state due to the lack of resources.
If you want to check about the specific incident you can review events around the nodes using the following commands:
kubectl get nodes
kubectl describe node <name_of_node>
kubectl get events n kubesystem
Coming to the notification option, at present, this feature is not there. However, this is already there in our roadmap. I don’t have a specific ETA for it. Our product team always look for such feature request and product feedback, I request you to vote/add on the idea here and subscribe for updates: https://ideas.digitalocean.com/ideas/
We use that page to help gauge demand for new features, so adding it, or adding your vote, will help us to prioritize when we can implement this feature.
I hope this helps!
Developer Support Engineer II, DigitalOcean