Issue that happens sometimes when cloning repo - Could not resolve host
Hey guys, I am using your chart for our pipelines. However recently there seems to be an issue that happens from time to time. When I start my pipeline the first step is to clone the repo in which it is run (not sure if this is the default behavior, as it's not configured in our pipeline). Sometimes this clone passes through without any issues and other times it fails with "fatal: unable to access 'https://gitlab.com/x/x/': Could not resolve host: gitlab.com". The error doesn't make sense for me, as this passes through without issues when restarted (with 0 changes form my end).
I will attach the gitlab-runner's values file:
gitlabUrl: https://gitlab.com/
runnerRegistrationToken: x
rbac:
create: true
clusterWideAccess: true
concurrent: 10
nodeSelector:
x: gitlab-runner-node-group
runners:
privileged: true
config: |-
[[runners]]
executor = "docker"
[runners.docker]
tls_verify = false
image = "docker:18.09.7"
memory = "2500m"
memory_reservation = "2300m"
cpus = "2"
oom_kill_disable = true
privileged = true
disable_entrypoint_overwrite = false
disable_cache = false
[runners.kubernetes.node_selector]
"x" = "gitlab-runner-node-group"
[runners.cache]
Type = "s3"
Path = "vendor/"
Shared = true
[runners.cache.s3]
ServerAddress = "x"
AccessKey = "x"
SecretKey = "x"
BucketName = "x"
BucketLocation = "x"
Insecure = false
Please let me know if you have some ideas what might be causing this.
Edited by Monika Radeva