Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Warning

This page was translated from the original Japanese version by PLaMo Translate. The Japanese version is authoritative; the English translation may contain inaccuracies.

Using Dedicated Nodes

Dedicated nodes are a specific type of compute node that can be reserved for your organization’s workloads. Pods created within your organization’s Namespace will be automatically scheduled on dedicated nodes unless explicitly specified to run on shared nodes see Shared Nodes. This eliminates the need for users to manually select nodes (by specifying a nodeSelector).

Dedicated nodes allocated to your organization can be accessed through the ReservedNode resource. The following command example lists all dedicated nodes assigned to your organization:

kubectl get reservednodes

The ReservedNode resource can be managed similarly to Kubernetes’ Node resource, allowing selection using either Label Selectors or Field Selectors. The fields supported by Field Selectors are as follows:

  • metadata.name
  • spec.unschedulable

Important note: The ReservedNode resource is read-only and cannot be modified.

Warning

Impact on Workloads During Maintenance

Be aware that maintenance activities involving compute node reboots may temporarily render some dedicated nodes unavailable.

  • For organizations with fewer than 4 dedicated node reservations, one node will be temporarily unavailable at a time. For 4 or more reservations, up to 25% (rounded down) of nodes may become temporarily unavailable.
  • Organizations with only one dedicated node reservation will experience complete node unavailability during maintenance.

For details on how maintenance activities may affect your workloads, please refer to the Maintenance Policy.