How to configure boot disk size for Spacelift worker pools

When deploying Spacelift worker pools, you may need to configure the boot disk size to ensure adequate storage space for your workloads. The approach varies depending on your cloud provider.

AWS EC2 Worker Pools

For AWS EC2 worker pools, you can control the boot disk size using the volume_size variable in the official Terraform module:

module "spacelift_workerpool" {
  source = "github.com/spacelift-io/terraform-aws-spacelift-workerpool-on-ec2?ref=v4.4.3"
  worker_pool_id   = var.worker_pool_id
  vpc_subnets      = var.worker_pool_subnets
  security_groups  = var.worker_pool_security_groups
  secure_env_vars  = {
    SPACELIFT_TOKEN            = var.worker_pool_config
    SPACELIFT_POOL_PRIVATE_KEY = var.worker_pool_private_key
  }
  volume_size = 100  # Boot disk set to 100 GB
}

GCP Worker Pools

The GCP worker pool module doesn't currently expose a boot disk size variable directly. To configure boot disk size for GCP worker pools, you'll need to:

1. Create a local fork of the GCP worker pool module

2. Add a boot_disk_size_gb variable to the google_compute_instance_template resource

3. Configure the boot disk size through this new variable

This approach allows you to maintain reproducible and manageable infrastructure code while customizing the boot disk size to meet your requirements.

When to Increase Boot Disk Size

Consider increasing the boot disk size if you encounter:

• Boot disk full errors preventing worker operations

• Large container images or dependencies that require additional storage

• Workloads that generate temporary files during execution

For immediate assistance with worker pool issues, you can also reach out through your dedicated Slack channel or raise a ticket on the support portal.