autoscaling-ec2-gitlab-runners-fargate
autoscaling-ec2-gitlab-runners-fargate copied to clipboard
woodjme
Autoscaling not happening?
I was expecting up to 12 (by default) ec2 instances to be spun up. This doesn't appear to be happening.
I'm not sure that request_concurrency is the correct option. The official docs are a bit vague.
Limit number of concurrent requests for new jobs from GitLab. Default is 1.
But here's the MR that added that option.
Instead, should we be configuring concurrent? Unfortunately, it looks like that isn't currently possible when registering.
See https://gitlab.com/gitlab-org/gitlab-runner/-/issues/1539
It also appears that setting request_concurrency is incompatible with --machine-idle-nodes 1 (which you can set via AdditionalRegisterParams) and triggers https://gitlab.com/gitlab-org/gitlab-runner/-/issues/2251
The environment variable needs renaming as the register command will pick it up even if you don't explicitly use --request-concurrency.
Noticed this as well.
I only see 1 job running per ECS task.
Does limit and IdleCount need to be configured?
https://docs.gitlab.com/runner/configuration/autoscale.html#how-concurrent-limit-and-idlecount-generate-the-upper-limit-of-running-machines
It looks like GitLab runners for EC2 and Fargate work differently.
https://docs.gitlab.com/runner/configuration/runner_autoscale_aws_fargate/