Upgrading Infrastructure and Worker Node VM Sizes in ARO

Solution Verified - Updated -

Environment

  • Azure Red Hat OpenShift (ARO)
    • V4

Issue

  • How to modify azure VM Sizes for worker and infrastructure nodes in an ARO cluster?
  • Is it possible to adjust azure VM sizes for ARO master nodes?
  • How to update Azure RedHat OpenShift worker and infrastructure node InstanceType.?

Resolution

Note : Upgrading or modifying VM sizes for worker nodes is possible within the ARO cluster. However, please be aware that this action is not applicable to the master nodes.

Kindly follow the below example to modify the VM size for worker nodes.

  1. Select the 'openshift-machine-api' project: :
$ oc project openshift-machine-api
  1. Editing the machineset :
$ oc edit machineset <name>

Showing an example here to change vmSize from Standard_D4s_v3 to Standard_D8s_v3 :

// Find the below line, where changes needed to be done :

          vmSize: Standard_D4s_v3

// Changing the value :

          vmSize: Standard_D8s_v3
  1. Cordoning a node (making a node temporarily unavailable for scheduling) :
$ oc adm cordon <nodename>
  1. Performing a node drain :
$ oc adm drain <nodename> --delete-emptydir-data --ignore-daemonsets
  1. Deleting the old node :
$ oc delete node <nodename>
  1. Deleting the machine (optional as the old machine will be deleted automatically):
$ oc delete machine <worker machine name>

Following these steps, the new machine will be created and added to the cluster. New nodes will be operational shortly. If necessary, the steps can be repeated for other machinesets once the new nodes are ready.

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