Outils pour utilisateurs

Outils du site


tech:pb_kubernetes_-_k8s_-_node_status_notready
,

Pb Kubernetes - K8S - Node status NotReady

Sur le Master

# kubectl get nodes
NAME   STATUS     ROLES    AGE   VERSION
kub1   Ready      master   40d   v1.17.0
kub2   NotReady   <none>   40d   v1.17.0
kub3   Ready      <none>   40d   v1.17.0

# kubectl describe node kub2
  Type             Status    LastHeartbeatTime                 LastTransitionTime                Reason              Message
  ----             ------    -----------------                 ------------------                ------              -------
  MemoryPressure   Unknown   Mon, 13 Jan 2020 14:05:22 +0100   Mon, 13 Jan 2020 14:09:07 +0100   NodeStatusUnknown   Kubelet stopped posting node status.
  DiskPressure     Unknown   Mon, 13 Jan 2020 14:05:22 +0100   Mon, 13 Jan 2020 14:09:07 +0100   NodeStatusUnknown   Kubelet stopped posting node status.
  PIDPressure      Unknown   Mon, 13 Jan 2020 14:05:22 +0100   Mon, 13 Jan 2020 14:09:07 +0100   NodeStatusUnknown   Kubelet stopped posting node status.
  Ready            Unknown   Mon, 13 Jan 2020 14:05:22 +0100   Mon, 13 Jan 2020 14:09:07 +0100   NodeStatusUnknown   Kubelet stopped posting node status.

Sur le Worker

root@kub2:~# systemctl status kubelet.service

root@kub2:~# journalctl -f -u kubelet.service
Jan 29 18:51:17 kub2 systemd[1]: Stopped kubelet: The Kubernetes Node Agent.
Jan 29 18:51:17 kub2 systemd[1]: Started kubelet: The Kubernetes Node Agent.
Jan 29 18:51:17 kub2 kubelet[15311]: F0129 18:51:17.486785   15311 server.go:198] failed to load Kubelet config file /var/lib/kubelet/config.yaml, error failed to read kubelet config file "/var/lib/kubelet/config.yaml", error: open /var/lib/kubelet/config.yaml: no such file or directory
Jan 29 18:51:17 kub2 systemd[1]: kubelet.service: Main process exited, code=exited, status=255/EXCEPTION
Jan 29 18:51:17 kub2 systemd[1]: kubelet.service: Failed with result 'exit-code'

Solution

Sur le Master

root@kub1:~# kubeadm token create --print-join-command
W0129 18:57:42.419029    4660 validation.go:28] Cannot validate kube-proxy config - no validator is available
W0129 18:57:42.419636    4660 validation.go:28] Cannot validate kubelet config - no validator is available
kubeadm join 192.168.56.21:6443 --token 2sfx5v.yjb8tsilc19u43rm     --discovery-token-ca-cert-hash sha256:f84fd4960fc7844182510b8daea9eb6739af2075f79edd726b3facfc1285e291

Sur le Worker

kubeadm join 192.168.56.21:6443 --token 2sfx5v.yjb8tsilc19u43rm     --discovery-token-ca-cert-hash sha256:f84fd4960fc7844182510b8daea9eb6739af2075f79edd726b3facfc1285e291
tech/pb_kubernetes_-_k8s_-_node_status_notready.txt · Dernière modification : de 127.0.0.1

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki