This is a cache of https://docs.openshift.com/container-platform/4.17/updating/updating_a_cluster/updating-hardware-on-nodes-running-on-vsphere.html. It is a snapshot of the page at 2024-11-24T06:20:35.197+0000.
Updating hardware on nodes running on vSphere - Performing a cluster update | Updating clusters | OpenShift Container Platform 4.17
    OpenShift docs are moving and will soon only be available at docs.redhat.com, the home of all Red Hat product documentation. Explore the new docs experience today.
  1. Documentation
    2. history bug_report picture_as_pdf
×

Updating hardware on nodes running on vSphere

You must ensure that your nodes running in vSphere are running on the hardware version supported by OpenShift Container Platform. Currently, hardware version 15 or later is supported for vSphere virtual machines in a cluster.

You can update your virtual hardware immediately or schedule an update in vCenter.

  • Version 4.17 of OpenShift Container Platform requires VMware virtual hardware version 15 or later.

  • Before upgrading OpenShift 4.12 to OpenShift 4.13, you must update vSphere to v7.0.2 or later; otherwise, the OpenShift 4.12 cluster is marked un-upgradeable.

Updating virtual hardware on vSphere

To update the hardware of your virtual machines (VMs) on VMware vSphere, update your virtual machines separately to reduce the risk of downtime for your cluster.

As of OpenShift Container Platform 4.13, VMware virtual hardware version 13 is no longer supported. You need to update to VMware version 15 or later for supporting functionality.

Updating the virtual hardware for control plane nodes on vSphere

To reduce the risk of downtime, it is recommended that control plane nodes be updated serially. This ensures that the Kubernetes API remains available and etcd retains quorum.

Prerequisites

  • You have cluster administrator permissions to execute the required permissions in the vCenter instance hosting your OpenShift Container Platform cluster.

  • Your vSphere ESXi hosts are version 7.0U2 or later.

Procedure

  1. List the control plane nodes in your cluster.

    $ oc get nodes -l node-role.kubernetes.io/master
    Example output
    NAME                    STATUS   ROLES    AGE   VERSION
control-plane-node-0    Ready    master   75m   v1.30.3
control-plane-node-1    Ready    master   75m   v1.30.3
control-plane-node-2    Ready    master   75m   v1.30.3

    Note the names of your control plane nodes.

  2. Mark the control plane node as unschedulable.

    $ oc adm cordon <control_plane_node>

  3. Shut down the virtual machine (VM) associated with the control plane node. Do this in the vSphere client by right-clicking the VM and selecting Power → Shut Down Guest OS. Do not shut down the VM using Power Off because it might not shut down safely.

  4. Update the VM in the vSphere client. Follow upgrade the Compatibility of a Virtual Machine Manually in the VMware documentation for more information.

  5. Power on the VM associated with the control plane node. Do this in the vSphere client by right-clicking the VM and selecting Power On.

  6. Wait for the node to report as Ready:

    $ oc wait --for=condition=Ready node/<control_plane_node>

  7. Mark the control plane node as schedulable again:

    $ oc adm uncordon <control_plane_node>

  8. Repeat this procedure for each control plane node in your cluster.

Updating the virtual hardware for compute nodes on vSphere

To reduce the risk of downtime, it is recommended that compute nodes be updated serially.

Multiple compute nodes can be updated in parallel given workloads are tolerant of having multiple nodes in a NotReady state. It is the responsibility of the administrator to ensure that the required compute nodes are available.
Prerequisites

  • You have cluster administrator permissions to execute the required permissions in the vCenter instance hosting your OpenShift Container Platform cluster.

  • Your vSphere ESXi hosts are version 7.0U2 or later.

Procedure

  1. List the compute nodes in your cluster.

    $ oc get nodes -l node-role.kubernetes.io/worker
    Example output
    NAME              STATUS   ROLES    AGE   VERSION
compute-node-0    Ready    worker   30m   v1.30.3
compute-node-1    Ready    worker   30m   v1.30.3
compute-node-2    Ready    worker   30m   v1.30.3

    Note the names of your compute nodes.

  2. Mark the compute node as unschedulable:

    $ oc adm cordon <compute_node>

  3. Evacuate the pods from the compute node. There are several ways to do this. For example, you can evacuate all or selected pods on a node:

    $ oc adm drain <compute_node> [--pod-selector=<pod_selector>]

    See the "Understanding how to evacuate pods on nodes" section for other options to evacuate pods from a node.

  4. Shut down the virtual machine (VM) associated with the compute node. Do this in the vSphere client by right-clicking the VM and selecting Power → Shut Down Guest OS. Do not shut down the VM using Power Off because it might not shut down safely.

  5. Update the VM in the vSphere client. Follow upgrade the Compatibility of a Virtual Machine Manually in the VMware documentation for more information.

  6. Power on the VM associated with the compute node. Do this in the vSphere client by right-clicking the VM and selecting Power On.

  7. Wait for the node to report as Ready:

    $ oc wait --for=condition=Ready node/<compute_node>

  8. Mark the compute node as schedulable again:

    $ oc adm uncordon <compute_node>

  9. Repeat this procedure for each compute node in your cluster.

Updating the virtual hardware for template on vSphere

Prerequisites

  • You have cluster administrator permissions to execute the required permissions in the vCenter instance hosting your OpenShift Container Platform cluster.

  • Your vSphere ESXi hosts are version 7.0U2 or later.

Procedure

  1. If the RHCOS template is configured as a vSphere template follow Convert a Template to a Virtual Machine in the VMware documentation prior to the next step.

    Once converted from a template, do not power on the virtual machine.

  2. Update the virtual machine (VM) in the VMware vSphere client. Complete the steps outlined in upgrade the Compatibility of a Virtual Machine Manually (VMware vSphere documentation).

  3. Convert the VM in the vSphere client to a template by right-clicking on the VM and then selecting Template → Convert to Template.

    The steps for converting a VM to a template might change in future vSphere documentation versions.
Additional resources

Scheduling an update for virtual hardware on vSphere

Virtual hardware updates can be scheduled to occur when a virtual machine is powered on or rebooted. You can schedule your virtual hardware updates exclusively in vCenter by following Schedule a Compatibility upgrade for a Virtual Machine in the VMware documentation.

When scheduling an update prior to performing an update of OpenShift Container Platform, the virtual hardware update occurs when the nodes are rebooted during the course of the OpenShift Container Platform update.