Restarting nodes on kubernetes as the node status shows unknown

+2 votes

The status of the node is coming as unknown right now

"conditions": [
          {
            "type": "Ready",
            "status": "Unknown",
            "lastHeartbeatTime": "2015-11-12T06:03:19Z",
            "lastTransitionTime": "2015-11-12T06:04:03Z",
            "reason": "Kubelet stopped posting node status."
          }

kubectl get nodes shows that the node is not ready. How do I fix this?

Oct 22, 2018 in Kubernetes by Atul
• 5,470 points

edited Oct 23, 2018 by Kalgi 1,701 views

5 answers to this question.

Your answer

Your name to display (optional):
Privacy: Your email address will only be used for sending these notifications.
0 votes

Considering that the node was previously working and recently stopped showing the ready status restart you kubelet service. Just ssh into the affected node and execute:

/etc/init.d/kubelet restart

Back on your master node run kubectl get nodes to check if the node is working now

answered Oct 22, 2018 by ajs3033
• 7,000 points
0 votes

Delete the node and then create a node object with the name of the one that died, bounce your schedulers & controllers, and then delete the node object. This seems to allow the scheduler to pick a new, good, node

answered Oct 23, 2018 by Kalgi
• 35,750 points
0 votes

You can try moving the cluster to the new node pool got rid of the weird stuck pods. But this is not the best solution, probably a temporary solution.

answered Oct 23, 2018 by lina
• 8,100 points
0 votes
I had faced a similar issue. In my case I had 10 nodes already up and running. I had created two new nodes and the status was stuck at unknown state. After a lot of research I figured I didnt have memory to deploy any more nodes. So in my case the memory was the issue. Try checking if you have sufficient memory.
answered Oct 23, 2018 by Karthik
0 votes
I had a similar issue, but mine was a very stupid silly mistake, I had made. On my node machine I had forgotten to unstall Docker engine. But what I still dont get it, is how did that node manage to join the cluster with having docker engine running on it?
answered Oct 23, 2018 by Zans

Related Questions In Kubernetes

0 votes
2 answers

The Status of nodes shown unknown

This worked for me In Azure, if you ...READ MORE

answered Aug 30, 2018 in Kubernetes by Nilesh
• 6,900 points
110 views
–1 vote
1 answer
0 votes
1 answer

Kubernetes- Jenkins slave node shows offline

TCP port for JNLP slave agent should ...READ MORE

answered Sep 5, 2018 in Kubernetes by Kalgi
• 35,750 points
364 views
0 votes
1 answer

permissions related to AWS ECR

if you add allowContainerRegistry: true, kops will add those permissions ...READ MORE

answered Oct 9, 2018 in Kubernetes by Kalgi
• 35,750 points
30 views
0 votes
1 answer
0 votes
3 answers

Error while joining cluster with node

Hi Kalgi after following above steps it ...READ MORE

answered Jan 17 in Others by anonymous
457 views
0 votes
1 answer

automating cluster setup and app deplument on kubernetes

Go through Google Cloud Deployment Manager. it automates ...READ MORE

answered Jul 5, 2018 in Kubernetes by ajs3033
• 7,000 points
26 views
+1 vote
4 answers

© 2018 Brain4ce Education Solutions Pvt. Ltd. All rights Reserved.
"PMP®","PMI®", "PMI-ACP®" and "PMBOK®" are registered marks of the Project Management Institute, Inc. MongoDB®, Mongo and the leaf logo are the registered trademarks of MongoDB, Inc.