OpenShift bootstrap node fails – kubelet cannot start due to missing `hyperkube` binary.

Solution Verified - Updated -

Issue

During OpenShift cluster installation, the bootstrap node fails to initialize. The kubelet service fails to start with the following error:

kubelet.sh[6271]: /usr/local/bin/kubelet.sh: line 7: /usr/bin/hyperkube: No such file or directory
systemd[1]: kubelet.service: Main process exited, code=exited, status=127/n/a
systemd[1]: kubelet.service: Failed with result 'exit-code'.
systemd[1]: Failed to start Kubernetes Kubelet.

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4.16+

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content