Dynamic concurrent runners fail while fetching repository.
I installed gitlab on Google cloud Kubernetes using the official helm (v3) chart. The gitalb-ci pipeline is composed of few concurrent jobs. After the runner ha started, the git clone (initial procedure) fails. This behaviour doesn’t happen if a single job runs. The repo has a dimension of 4 giga bytes.
It seems a timeout issue, but I don’t find any specific solution. Moreover, this happens only if multiple jobs run in parallel.
Here the chart configurations while installing the release:
–install gitlab gitlab/gitlab
–timeout 20m
–set global.hosts.domain=**********
–set global.hosts.externalIP=************
–set certmanager-issuer.email=**********
–set postgresql.install=false
–set global.psql.host=*********
–set global.psql.database=*********
–set global.psql.username=************
–set global.psql.password.secret=**********
–set global.psql.password.key=***********
–set ingress.proxyBodySize=10G
–set redis.cluster.enabled=true
–set global.minio.enabled=true
–set gitlab-runner.runners.privileged=true
–set gitlab-runner.concurrent=25
–set gitlab-runner.runners.builds.cpuLimit=2000m
–set gitlab-runner.runners.builds.memoryLimit=2Gi
–set gitlab-runner.runners.builds.cpuRequests=1000m
–set gitlab-runner.runners.builds.memoryRequests=1Gi
–set gitlab-runner.runners.service.cpuLimit=2000m
–set gitlab-runner.runners.service.memoryLimit=2Gi
–set gitlab-runner.runners.service.cpuRequests=1000m
–set gitlab-runner.runners.service.memoryRequests=1Gi
–set gitlab-runner.resources.limits.cpu=2000m
–set gitlab-runner.resources.limits.memory=2Gi
–set gitlab-runner.resources.requests.cpu=1000m
–set gitlab-runner.resources.requests.memory=1Gi
Thanks a lot for your help