From the course: Debugging Kubernetes

Unlock the full course today

Join today to access over 24,900 courses taught by industry experts.

Understanding NotReady Kubernetes nodes

Understanding NotReady Kubernetes nodes - Kubernetes Tutorial

From the course: Debugging Kubernetes

Start my 1-month free trial Buy for my team

Understanding NotReady Kubernetes nodes

“

- [Instructor] Many of the Kubernetes clusters that you'll work with will have control-planes that are managed by cloud providers. While you won't have the ability to configure or troubleshoot control-plane components, you also won't have to deal with the administrative overhead that comes with that. However, you'll still be responsible for adding workers to those clusters. This is usually easy and painless to do. However, there are times when you try to join a new worker and no matter what you do, you just can't get it out of a NotReady state. This commonly happens for three reasons. Either the kubelet service running on the node can't communicate with the cluster's API server, the kubelet service on the node is misconfigured or not started, or the Container Network Interface, or CNI for short, that was installed into the kubelet is misconfigured. For the first scenario, you can use the network troubleshooting techniques we learned about in understanding slow kubectl commands…

Contents