K
Q

Worker Nodes showing up as NotReady after upgrade to latest K8 version

3/7/2019

Worker nodes upgraded to latest k8s version and I am facing the 'NotReady' status of those worker nodes. I see 'PIDPressure - False' when I do a 'kubectl describe' for these nodes.

-- ravi kiran mahankali
kubernetes

Similar Questions

Changing the Key to the kops cluster doesn't let me ssh to master nodes from bastion host
Why can I not remove my permissions on kubeadm?
Cloudformation for a kube2iam role
How do I set multiple commands in config.yaml in kubernetes?

2 Answers

4/28/2019

Deleting the stale Docker containers on the K8s nodes and restarting the services has resolved my issue. Upgrading to latest K8s is not necessary.

-- ravi kiran mahankali
Source: StackOverflow
3/7/2019

PIDPressure - False

^^ is an expected condition of the healthy node, it means that kubelet has sufficient PIDs available for normal operation.

Need more details:

  • Kubelet version? kubectl version
  • Can you share a full output of the describe command? kubectl describe node <node-name>
  • ssh to the node and run sudo journalctl -u kubelet --all|tail
-- A_Suh
Source: StackOverflow