- GitLab Runner Autoscaler
- Configure the runner manager
- Configure runner autoscaling executors
You can use GitLab Runner autoscaling to automatically scale the runner on public cloud instances. When you configure a runner to use an autoscaler, you can manage increases in CI/CD job load by leveraging your cloud infrastructure to run multiple jobs simultaneously.
In addition to the autoscaling options for public cloud instances, you can use the following container orchestration solutions for hosting and scaling a runner fleet.
- Red Hat OpenShift Kubernetes clusters
- Kubernetes clusters: AWS EKS, Azure, on-premise
- Amazon Elastic Container Services clusters on AWS Fargate
GitLab Runner Autoscaler is the successor to the autoscaling technology based on Docker Machine. The components of the GitLab Runner Autoscaler are:
- Taskscaler: Manages the autoscaling logic, bookkeeping, and creates fleets for runner instances that use cloud provider autoscaling groups of instances.
- Fleeting: An abstraction for cloud provider virtual machines.
- Cloud provider plugin: Handles the API calls to the target cloud platform and is implemented using a plugin development framework.
The following autoscaling options are supported for public cloud compute instances.
|Next Runner Autoscaler (Beta)||GitLab Runner Docker Machine Autoscaler (GA)|
|Amazon Web Services EC2 instances||Yes||Yes|
|Google Compute Engine||Yes||Yes|
|Microsoft Azure Virtual Machines||Yes||Yes|
|Docker Autoscaler executor||Yes||No||Yes|
You must configure the runner manager to use GitLab Runner Autoscaling, both the Docker Machine Autoscaling solution and the GitLab Runner Autoscaler.
The runner manager is a type of runner that creates multiple runners for autoscaling. It continuously polls GitLab for jobs and interacts with the public cloud infrastructure to create a new instance to execute jobs. The runner manager must run on a host machine that has GitLab Runner installed. Choose a distribution that Docker and GitLab Runner supports, like Ubuntu, Debian, CentOS, or RHEL.
- Create an instance to host the runner manager. This must not be a spot instance (AWS), or spot virtual machine (GCP, Azure).
- Install GitLab Runner on the instance.
- Add the cloud provider credentials to the Runner Manager host machine.
## credentials_file [default] aws_access_key_id=__REDACTED__ aws_secret_access_key=__REDACTED__
This snippet is in the runners.machine section of the
[runners.machine] IdleCount = 1 IdleTime = 1800 MaxBuilds = 10 MachineDriver = "amazonec2" MachineName = "gitlab-docker-machine-%s" MachineOptions = [ "amazonec2-access-key=XXXX", "amazonec2-secret-key=XXXX", "amazonec2-region=us-central-1", "amazonec2-vpc-id=vpc-xxxxx", "amazonec2-subnet-id=subnet-xxxxx", "amazonec2-zone=x", "amazonec2-use-private-address=true", "amazonec2-security-group=xxxxx", ]
After you configure the runner manager, configure the executors specific to autoscaling: