Add a node pool

​

Creating a scalable node pool in EKS

1. Create a new-nodegroup.yaml file like the one below, and configure it with the properties you want the new group to have. All values shown with a $ are variables that you must modify. You choose $NODE_POOL_NAME: it becomes the value of the dominodatalab.com/node-pool node label, and you enter the same value in the Node Pool field when you create a hardware tier so Domino schedules executions from that tier onto these nodes.
   apiVersion: eksctl.io/v1alpha5
   kind: ClusterConfig
   metadata:
     name: $CLUSTER_NAME
     region: $CLUSTER_REGION
   nodeGroups:
     - name: $GROUP_NAME # this can be any name you choose, it will be part of the ASG and template name
       instanceType: $AWS_INSTANCE_TYPE
       minSize: $DMINIMUM_GROUP_SIZE
       maxSize: $DESIRED_MAXIMUM_GROUP_SIZE
       volumeSize: 400 # important to allow for image caching on Domino workers
       availabilityZones: ["$YOUR_CHOICE"] # this should be the same AZ (or the same multiple AZ's) as your other node pools
       ami:
         $AMI_ID
       labels:
         "dominodatalab.com/node-pool": "$NODE_POOL_NAME" # admin-chosen label; enter the same value in the Node Pool field of the hardware tier
         # "nvidia.com/gpu": "true" # uncomment this line if this pool uses a GPU instance type
       tags:
         "k8s.io/cluster-autoscaler/node-template/label/dominodatalab.com/node-pool": "$NODE_POOL_NAME"
         # "k8s.io/cluster-autoscaler/node-template/label/nvidia.com/gpu": "true" # uncomment this line if this pool uses a GPU instance type
   
   The AWS tag with key k8s.io/cluster-autoscaler/node-template/label/dominodatalab.com/node-pool is important for exposing the group to your cluster autoscaler. You cannot have compute node pools in separate, isolated AZs, as this creates volume affinity errors.
2. Once your configuration file describes the group you want to create, run eksctl create nodegroup --config-file=new-nodegroup.yaml.
3. Take the names of the resulting ASG and add them to the autoscaling.groups section of your domino.yml installer configuration.
4. Run the Domino installer to update the autoscaler.
5. Create a new hardware tier or model resource quota in Domino that references the new labels.