<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "bug" label. For the Community Edition issue tracker: - https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name%5B%5D=bug For the Enterprise Edition issue tracker: - https://gitlab.com/gitlab-org/gitlab-ee/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab-ee/issues?label_name%5B%5D=bug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary Our CI runs tests using the mongo service and this works fine on the shared runners. I recently installed the GitLAB runner helm chart and added a group runner. Whenever the job is executed by this runner the test fail. The error is: MongoNetworkError: failed to connect to server [mongo:27017] on first connect [MongoNetworkError: getaddrinfo EAI_AGAIN mongo mongo:27017] ### Steps to reproduce Use the mongo service on a non-shared Kubernetes runner ### What is the current *bug* behavior? MongoNetworkError: failed to connect to server [mongo:27017] on first connect [MongoNetworkError: getaddrinfo EAI_AGAIN mongo mongo:27017] ### What is the expected *correct* behavior? Connect to MongoDB correctly ### Output of checks This bug happens on GitLab.com but with our own runner on an Azure Kubernetes cluster