GracefulRebootRequest resource

This section describes the GracefulRebootRequest custom resource (CR) used in the management API for a rolling reboot of several or all cluster machines without workloads interruption. The resource is also useful for a bulk reboot of machines, for example, on large clusters.

The GracefulRebootRequest CR contains the following fields:

  • apiVersion

    API version of the object that is kaas.mirantis.com/v1alpha1.

  • kind

    Object type that is GracefulRebootRequest.

  • metadata

    Metadata of the GracefulRebootRequest CR that contains the following fields:

    • name

      Name of the GracefulRebootRequest object. The object name must match the name of the cluster on which you want to reboot machines.

    • namespace

      Project where the GracefulRebootRequest is created.

  • spec

    Specification of the GracefulRebootRequest CR that contains the following fields:

    • machines

      List of machines for a rolling reboot. Each machine of the list is cordoned, drained, rebooted, and uncordoned in the order of cluster upgrade policy. For details about the upgrade order, see Change the upgrade order of a machine.

      Leave this field empty to reboot all cluster machines.

      Caution

      The cluster and machines must have the Ready status to perform a graceful reboot.

Configuration example:

apiVersion: kaas.mirantis.com/v1alpha1
kind: GracefulRebootRequest
metadata:
  name: demo-cluster
  namespace: demo-project
spec:
  machines:
  - demo-worker-machine-1
  - demo-worker-machine-3

Caution

When rebooting both the Kubernetes and OpenStack control plane machines, either by specifying machines of both types in spec.machines or by leaving the list empty, the two node groups may be rebooted in parallel, which can cause issues with workload management. To avoid this, perform the reboot in two sequential steps as described in: Perform a rolling reboot of a cluster using CLI.