GitLab Runner are not running because a issue with DNS.
Steps to reproduce
minikube start \
  --cpus 4 \
  --disk-size 40g \
  --host-only-cidr '10.100.1.1/24' \
  --memory 8192 \
  --vm-driver hyperkit$ helm list                                                                                                                                                                     
NAME         	REVISION	UPDATED                 	STATUS  	CHART               	APP VERSION	NAMESPACE
cert-manager 	1       	Sat Jul 27 15:34:06 2019	DEPLOYED	cert-manager-v0.8.1 	v0.8.1     	cert-manager
gitlab-ce    	2       	Sat Jul 27 16:27:00 2019	DEPLOYED	gitlab-2.1.1        	12.1.1     	gitlab
nginx-ingress	1       	Sat Jul 27 14:36:49 2019	DEPLOYED	nginx-ingress-1.11.3	0.25.0     	nginx-ingressConfiguration used
helm install gitlab/gitlab \
  -n gitlab-ce \
  --namespace gitlab \
  --set global.edition=ce \
  --set global.ingress.configureCertmanager=false \
  --set global.ingress.class=nginx \
  --set nginx-ingress.enabled=false \
  --set certmanager.install=falseVersions
- Chart: gitlab-2.1.1
- Platform:
- Self-hosted: Minikube
 
- Kubernetes:
- Client: v1.15.1
- Server: v1.15.0
 
- Helm:
- Client: v2.14.2
- Server: v2.14.2
 
Relevant logs
$ kubectl logs gitlab-ce-gitlab-runner-6995cb4956-z46tw                                                                                                                          
Registration attempt 1 of 30
Runtime platform                                    arch=amd64 os=linux pid=12 revision=de7731dd version=12.1.0
WARNING: Running in user-mode.
WARNING: The user-mode requires you to manually start builds processing:
WARNING: $ gitlab-runner run
WARNING: Use sudo for system-mode:
WARNING: $ sudo gitlab-runner...
ERROR: Registering runner... failed                 runner=oJbKhXph status=couldn't execute POST against https://gitlab.example.com/api/v4/runners: Post https://gitlab.example.com/api/v4/runners: dial tcp: lookup gitlab.example.com on 10.96.0.10:53: server misbehaving
PANIC: Failed to register this runner. Perhaps you are having network problems$ kubectl describe endpoints kube-dns -n kube-system                                                                                                                             17:58:16
Name:         kube-dns
Namespace:    kube-system
Labels:       k8s-app=kube-dns
              kubernetes.io/cluster-service=true
              kubernetes.io/name=KubeDNS
Annotations:  endpoints.kubernetes.io/last-change-trigger-time: 2019-07-27T17:22:42Z
Subsets:
  Addresses:          172.17.0.2,172.17.0.3
  NotReadyAddresses:  <none>
  Ports:
    Name     Port  Protocol
    ----     ----  --------
    dns      53    UDP
    dns-tcp  53    TCP
    metrics  9153  TCP
Events:  <none>