Cluster is down due to kubelet.go:XXX] node "XXXXXX" not found and no serving certificate available for the kubelet

Solution Verified - Updated -

Issue

  • Cluster is down and following logs observer in journalctl logs.
May 12 21:15:15 Hostname hyperkube[34705]: E0512 21:15:15.122157   34705 kubelet.go:2254] node "Hostname" not found
May 12 21:15:15 Hostname hyperkube[34705]: I0512 21:15:15.128554   34705 log.go:172] http: TLS handshake error from XX.XX.XX.XX:XXXXX: no serving certificate available for the kubelet
May 12 21:15:15 Hostname hyperkube[34705]: E0512 21:15:15.222426   34705 kubelet.go:2254] node "Hostname" not found

Environment

  • Red Hat OpenShift Container Platform 4.2

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In