Soon, all Red Hat OpenShift documentation will only be available on docs.redhat.com, the official location of all Red Hat product documentation. Get familiar with the updated experience today!
  1. Documentation
×

Modifying a machine set

You can modify a machine set, such as adding labels, changing the instance type, or changing block storage.

On oVirt, you can also change a machine set to provision new nodes on a different storage domain.

If you need to scale a machine set without making other changes, see Manually scaling a machine set.

Modifying a machine set

To make changes to a machine set, edit the MachineSet YAML. Then, remove all machines associated with the machine set by deleting each machine or scaling down the machine set to 0 replicas. Then, scale the replicas back to the desired number. Changes you make to a machine set do not affect existing machines.

If you need to scale a machine set without making other changes, you do not need to delete the machines.

By default, the OKD router pods are deployed on workers. Because the router is required to access some cluster resources, including the web console, do not scale the worker machine set to 0 unless you first relocate the router pods.
Prerequisites

  • Install an OKD cluster and the oc command line.

  • Log in to oc as a user with cluster-admin permission.

Procedure

  1. Edit the machine set:

    $ oc edit machineset <machineset> -n openshift-machine-api

  2. Scale down the machine set to 0:

    $ oc scale --replicas=0 machineset <machineset> -n openshift-machine-api

    Or:

    $ oc edit machineset <machineset> -n openshift-machine-api

    You can alternatively apply the following YAML to scale the machine set:

    apiVersion: machine.openshift.io/v1beta1
kind: MachineSet
metadata:
  name: <machineset>
  namespace: openshift-machine-api
spec:
  replicas: 0

    Wait for the machines to be removed.

  3. Scale up the machine set as needed:

    $ oc scale --replicas=2 machineset <machineset> -n openshift-machine-api

    Or:

    $ oc edit machineset <machineset> -n openshift-machine-api

    You can alternatively apply the following YAML to scale the machine set:

    apiVersion: machine.openshift.io/v1beta1
kind: MachineSet
metadata:
  name: <machineset>
  namespace: openshift-machine-api
spec:
  replicas: 2

    Wait for the machines to start. The new machines contain changes you made to the machine set.

Migrating nodes to a different storage domain on oVirt

You can migrate the OKD control plane and compute nodes to a different storage domain in a oVirt cluster.

Migrating compute nodes to a different storage domain in oVirt

Prerequisites

  • You are logged in to the Engine.

  • You have the name of the target storage domain.

Procedure

  1. Identify the virtual machine template:

    $ oc get -o jsonpath='{.items[0].spec.template.spec.providerSpec.value.template_name}{"\n"}' machineset -A

  2. Create a new virtual machine in the Engine, based on the template you identified. Leave all other settings unchanged. For details, see Creating a Virtual Machine Based on a Template in the Red Hat Virtualization Virtual Machine Management Guide.

    You do not need to start the new virtual machine.

  3. Create a new template from the new virtual machine. Specify the target storage domain under Target. For details, see Creating a Template in the Red Hat Virtualization Virtual Machine Management Guide.

  4. Add a new machine set to the OKD cluster with the new template.

    1. Get the details of the current machine set:

      $ oc get machineset -o yaml

    2. Use these details to create a machine set. For more information see Creating a machine set.

      Enter the new virtual machine template name in the template_name field. Use the same template name you used in the New template dialog in the Engine.

    3. Note the names of both the old and new machine sets. You need to refer to them in subsequent steps.

  5. Migrate the workloads.

    1. Scale up the new machine set. For details on manually scaling machine sets, see Scaling a machine set manually.

      OKD moves the pods to an available worker when the old machine is removed.

    2. Scale down the old machine set.

  6. Remove the old machine set:

    $ oc delete machineset <machineset-name>
Additional resources

Migrating control plane nodes to a different storage domain on oVirt

OKD does not manage control plane nodes, so they are easier to migrate than compute nodes. You can migrate them like any other virtual machine on oVirt.

Perform this procedure for each node separately.

Prerequisites

  • You are logged in to the Engine.

  • You have identified the control plane nodes. They are labeled master in the Engine.

Procedure

  1. Select the virtual machine labeled master.

  2. Shut down the virtual machine.

  3. Click the Disks tab.

  4. Click the virtual machine’s disk.

  5. Click More Actionskebab and select Move.

  6. Select the target storage domain and wait for the migration process to complete.

  7. Start the virtual machine.

  8. Verify that the OKD cluster is stable:

    $ oc get nodes

    The output should display the node with the status Ready.

  9. Repeat this procedure for each control plane node.