I created a self-hosted GitLab instance using the helm chart (https://charts.gitlab.io/ v4.11.3), and external Let’s Encrypt and Cert-Manager for Ingress. The helm chart is installed via a parent chart, thus the
gitlab section. Every CI task fails with a timeout fetching the git repo. I have tried many different tweaks to the .gitlab-ci.yml to no avail. I am able to access GitLab just fine in the Kubernetes cluster and on my workstation. What could be the issue of the runner timing out?
Getting source from Git repository Fetching changes with git depth set to 50... Initialized empty Git repository in xxxxxx Created fresh repository. fatal: unable to access 'https://gitlab.xxxx.com/xxxx/xxxx.git/': Failed to connect to gitlab.xxxx.com port 443: Operation timed out Cleaning up file based variables00:00 ERROR: Job failed: command terminated with exit code 1
global: logLevel: debug hosts: domain: xxxx.com ingress: annotations: cert-manager.io/cluster-issuer: letsencrypt-prod kubernetes.io/tls-acme: true class: nginx configureCertmanager: false gitlab: certmanager: install: false gitlab: webservice: ingress: tls: secretName: gitlab-webservice-tls nginx-ingress: enabled: false registry: ingress: tls: secretName: gitlab-registry-tls minio: ingress: tls: secretName: gitlab-minio-tls
image: name: alpine/helm:3.5.4 entrypoint: ["/bin/sh", "-c"] variables: FF_GITLAB_REGISTRY_HELPER_IMAGE: 1 stages: - lint-helm-chart lint-helm: stage: lint-helm-chart script: - helm lint