Increasing System Resources (RAM/CPU) doesn't reflect in OpenShift 4.x cluster when increased from backend in VMware vSphere

Solution Verified - Updated -

Environment

  • Red Hat Openshift Container Platform (RHOCP)
    • 4
  • VMware vSphere

Issue

  • CPU/memory resources are increased from backend, but doesn't reflect up in OpenShift cluster (Hot Memory/CPU)

Resolution

  • This is a workaround and not recommended by Red Hat . Only option is to re-provision your nodes with additional resources.

  • Once CPU/Memory is modified from vSphere and it's visible in Nodes, a restart of kubelet service will reflect updated CPU/Memory status in OpenShift.

    $ oc debug node/<node-name>
$ chroot /host
# systemctl restart kubelet.service

  • An RFE is already in place to support hot memory/CPU feature. Please open a support case with Red Hat to know the status of RFE at Red Hat Customer Portal

Root Cause

  • By default kubelet holds up configuration in it's memory and it will not reflect changes done from background to nodes unless it's loaded again so even if memory/cpu is added from backend on the fly, it will not display it in OpenShift cluster(in case node is not rebooted).

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments