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

NodePIDPressure condition should set to unknown when node lost connnection with contorl #68643

Open
Pingan2017 opened this Issue Sep 14, 2018 · 1 comment

Comments

Projects
None yet
3 participants
@Pingan2017
Contributor

Pingan2017 commented Sep 14, 2018

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug

/kind feature

What happened:
when the node lost connection with master , using 'kubectl describe node' find the NodePIDPressure is false , no switch to unknown.

Conditions:
  Type              Status    LastHeartbeatTime                 LastTransitionTime                Reason                                                             Message
  ----              ------    -----------------                 ------------------                ------                                                             -------
  OutOfDisk         Unknown   Fri, 14 Sep 2018 17:39:56 +0800   Fri, 14 Sep 2018 17:40:40 +0800   NodeStatusUnknown                                                  Kubelet stopped posting node status.
  MemoryPressure    Unknown   Fri, 14 Sep 2018 17:39:56 +0800   Fri, 14 Sep 2018 17:40:40 +0800   NodeStatusUnknown                                                  Kubelet stopped posting node status.
  DiskPressure      Unknown   Fri, 14 Sep 2018 17:39:56 +0800   Fri, 14 Sep 2018 17:40:40 +0800   NodeStatusUnknown                                                  Kubelet stopped posting node status.
  Ready             Unknown   Fri, 14 Sep 2018 17:39:56 +0800   Fri, 14 Sep 2018 17:40:40 +0800   NodeStatusUnknown                                                  Kubelet stopped posting node status.
  PIDPressure       False     Fri, 14 Sep 2018 17:39:56 +0800   Fri, 14 Sep 2018 17:38:46 +0800   KubeletHasSufficientPID                                            kubelet has sufficient PID available

What you expected to happen:
PIDPressure Unknown Fri, 14 Sep 2018 05:13:09 +0800 Fri, 14 Sep 2018 05:13:53 +0800 NodeStatusUnknown Kubelet stopped posting node status.
How to reproduce it (as minimally and precisely as possible):
stop kubelet, wait the node Notready
check the node status 'kubectl describe node'
Anything else we need to know?:

Environment:

  • Kubernetes version (use kubectl version):
  • Cloud provider or hardware configuration:
  • OS (e.g. from /etc/os-release):
  • Kernel (e.g. uname -a):
  • Install tools:
  • Others:
@k82cn

This comment has been minimized.

Show comment
Hide comment
@k82cn

k82cn Sep 14, 2018

Member

/sig node

Member

k82cn commented Sep 14, 2018

/sig node

@k8s-ci-robot k8s-ci-robot added sig/node and removed needs-sig labels Sep 14, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment