Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kubelet stopped posting node status #77943

Open
absinabs opened this issue May 15, 2019 · 4 comments

Comments

Projects
None yet
5 participants
@absinabs
Copy link

commented May 15, 2019


name: Bug Report
about: Report a bug encountered while operating Kubernetes
labels: kind/bug


What happened: We are doing some Poc on the hybrid kubernaties cluster (with windows and linux node) after creating the cluster with 2 windows and 2 linux it went fine and we were able to run our windows container in the pods on the node after 45 hours the windows node start showing not ready status ,though Cluster is still running . when we try to see the windows node with describe command it is showing like Node NotReady status with "Kubelet stopped posting node status" also we were not able to create new pods as they are going in to pending state.

What you expected to happen: It should remain in ready satus as the other linux nodes

How to reproduce it (as minimally and precisely as possible):
we are currently following the windows doc step by step from creating the cluster to joining the windows node below is the link

https://docs.microsoft.com/en-us/virtualization/windowscontainers/kubernetes/getting-started-kubernetes-windows

Anything else we need to know?:

Environment:

  • Kubernetes version (use kubectl version): 1.14
  • Cloud provider or hardware configuration: AWS and EC2 xlarge
  • OS (e.g: cat /etc/os-release): Master and linux nodes ubuntu 16.04 and windows server 2019
  • Kernel (e.g. uname -a):
  • Install tools: Docker on all the nodes and master
  • Network plugin and version (if this is a network-related bug): we are using Flannel in vxlan mode for windows
  • Others:
@athenabot

This comment has been minimized.

Copy link

commented May 15, 2019

/sig windows
/sig node

These SIGs are my best guesses for this issue. Please comment /remove-sig <name> if I am incorrect about one.

🤖 I am a bot run by vllry. 👩‍🔬

@daschott

This comment has been minimized.

Copy link

commented May 15, 2019

@absinabs is kubelet still running on the node? What do the kubelet logs say?

@mattjmcnaughton

This comment has been minimized.

Copy link
Contributor

commented May 16, 2019

@absinabs

Thanks for reaching out :) Would you mind updating your issue so that it follows the issue template? Here's a link to the template: https://github.com/kubernetes/kubernetes/blob/master/.github/ISSUE_TEMPLATE/bug-report.md

@absinabs absinabs changed the title I am able to create a Hybrid cluster with a windows node and with kubectl get nodes command my windows node is there with "Ready" state, however after few hours the windows node in the Cluster starts showing the "Not ready" status and when we try to see the Node with describe command it is showing like Node `NotReady` status with "Kubelet stopped posting node status" any idea how to resolve the issue Kubelet stopped posting node status May 16, 2019

@absinabs

This comment has been minimized.

Copy link
Author

commented May 16, 2019

@absinabs is kubelet still running on the node? What do the kubelet logs say?

@absinabs absinabs closed this May 16, 2019

@absinabs absinabs reopened this May 16, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.