Manage node pools

​

Manage node pools

• Node pool: The name of the node pool.
• Data plane: The data plane where the node pool is located.
• Accelerator type: The accelerator used by the node pool. It can be CPU only, GPU, or Neuron.
• Architecture: The CPU architecture of the instances in the node pool, AMD64 or ARM64. This column appears on deployments with multi-architecture support enabled.
• Instance types: The instance types configured in the node pool.
• Max CPU: The maximum number of virtual CPUs the node pool can use, if a limit is set.
• Max memory: The maximum amount of memory the node pool can use, if a limit is set.
• Support spot: Whether the node pool supports spot instances.
• Hardware tiers: The number of hardware tiers that have configured this node pool.
• Description: A description of the node pool.

​

Add a new node pool

1. To add a new node pool, click the Add Node Pool button.
2. In the Add Node Pool dialog, fill in the following fields:
   • Name: The name of the node pool.
   • Description: A description of the node pool.
   • Data plane: The data plane where the node pool is created.
   • Accelerator type: The accelerator type for the node pool. It can be CPU only, GPU, or Neuron.
   • Architecture: The CPU architecture of the instances in the node pool, either AMD64 or ARM64. This option appears on deployments with multi-architecture support enabled. Domino applies the architecture to the node pool’s scheduling requirements through the kubernetes.io/arch node label. Node pools created before this field existed use amd64. Match the architecture of the hardware tiers that use the node pool.
   Node pools use the amd64 CPU architecture by default. On data planes that provide Arm-based instance types, you can create arm64 node pools with the CPU only or GPU accelerator type. Neuron accelerators are available only on amd64 node pools, so Domino rejects a node pool that combines Neuron with arm64.
3. Select the instance types you want to add to the node pool by checking the checkboxes next to the instance types. The table shows only instance types that match the architecture you selected, in the Architecture column. If you change the architecture, Domino clears your instance type selections. Domino also rejects a node pool whose instance types use a different architecture, or that are not available in the data plane’s region. For each instance type, you see the following information:
   • Instance type: The name of the instance type.
   • vCPUs: The number of virtual CPUs in the instance type.
   • Memory (GiB): The amount of memory in the instance type.
   • GPU count: The number of GPUs in the instance type, if applicable.
   • Est. hourly rate: An estimate of the cost per hour for the instance type.
4. You can set the limits for the node pool in the Set Limits section. The limits are the maximum number of nodes that can be created in the node pool. This helps you to avoid creating a large number of nodes and helps keep costs under control. Limits are defined by the following fields:
   • Maximum CPU: The maximum number of virtual CPUs that can be used in the node pool (integer).
   • Maximum memory: The maximum amount of memory that can be used in the node pool (binary SI units, for example, 16Gi; see Binary SI).
     To limit the node pool to a number of instances, you can multiply the vCPU value of the instance type by the number of instances you want to limit the node pool to. For example, if you want to limit the node pool to 10 instances of c5.2xlarge, you can set the maximum CPU to 80 (10 * 8 vCPUs).
     
5. Click the Create Node Pool button to create the node pool.

​

Edit a node pool

1. In the node pools table, click the three dots menu in the node pool row and select Edit.
2. In the Edit Node Pool dialog, update any of the following fields:
   • Description: The description of the node pool.
   • Maximum CPU: The maximum number of virtual CPUs the node pool can use (integer). Leave empty to remove the limit.
   • Maximum memory: The maximum amount of memory the node pool can use, in binary SI units, for example 16Gi. Leave empty to remove the limit. See Binary SI.
3. Click Save to apply the changes. Any field you leave unchanged keeps its current value. To clear an existing description or limit, empty the field before saving.

​

Delete a node pool

1. If the node pool is not used by any hardware tier, you can delete it by clicking the three dots menu in node pool row and selecting Delete.
2. A confirmation dialog appears. You see one of the following messages:
   1. If the node pool is not being used by any hardware tier: You can delete it by clicking the Remove node pool button.
   2. If the node pool is used by some hardware tier: You can click each hardware tier name to go to the hardware tier configuration page and remove the node pool from the hardware tier. Once the node pool is not used by any hardware tier, you can delete it by clicking the I’ve updated the hardware tiers button.