Gitlab installation on kubernetes (on AWS) fails with/without provisioning certs
I am trying to setup gitlab on kubernetes cluster with helm as instructed in the docs. But somehow, the setup fails while creating certificates with cert-manager for the domains.
Here's what I did:
- Create a separate namespace for install gitlab
- Run helm command to install gitlab in above namespace
- Once ingress is provisioned, create a wildcard DNS entry with the existing AWS LB endpoint
I know I might be doing something wrong here. But, there is no mention of anything related to custom kubernetes clusters created on AWS. It's all about GKE,EKS and AKS. Any hint about what might be going wrong would be appreciated as I've spent considerable time for getting gitlab running without any success at all.
Error:
http-01 self check failed for domain "gitlab.xyz.net"
More information: The health checks for Load Balancer also keeps failing. So, even with using self-signed certificates, the installation is failing.
When tried to ssh into one of the nodes and check return status, here's what I saw:
$ curl -v localhost:32030/healthz
* Trying 127.0.0.1...
* Connected to localhost (127.0.0.1) port 32030 (#0)
> GET /healthz HTTP/1.1
> Host: localhost:32030
> User-Agent: curl/7.47.0
> Accept: */*
>
< HTTP/1.1 503 Service Unavailable
< Content-Type: application/json
< Date: Mon, 19 Nov 2018 13:38:49 GMT
< Content-Length: 114
<
{
"service": {
"namespace": "gitlab-ci",
"name": "gitlab-nginx-ingress-controller"
},
"localEndpoints": 0
* Connection #0 to host localhost left intact
}
And, when I checked ingress controller service, it was up and running:
gitlab-nginx-ingress-controller LoadBalancer 10.43.168.81 XXXXXXXXXXXXXX.us-east-2.elb.amazonaws.com 80:32006/TCP,443:31402/TCP,22:31858/TCP
P.S. The deprecated charts works like charm.