无法在Kubernetes上安装gitlab

时间:2018-11-18 14:32:19

标签: kubernetes gitlab gitlab-ci

我正在尝试在已经具有入口(由RKE创建的集群)的kubernetes集群上安装带有头盔的gitlab。使用gitlab,我想将其部署到单独的命名空间中。为此,我运行了以下命令:

$ gitlab-config helm upgrade --install gitlab gitlab/gitlab \
--timeout 600 \
--set global.hosts.domain=asdsa.asdasd.net \
--set certmanager-issuer.email=sd@cloudssky.com \
--set global.edition=ce \
--namespace gitlab-ci \
--set gitlab.migrations.image.repository=registry.gitlab.com/gitlab-org/build/cng/gitlab-rails-ce \
--set gitlab.sidekiq.image.repository=registry.gitlab.com/gitlab-org/build/cng/gitlab-sidekiq-ce \
--set gitlab.unicorn.image.repository=registry.gitlab.com/gitlab-org/build/cng/gitlab-unicorn-ce \
--set gitlab.unicorn.workhorse.image=registry.gitlab.com/gitlab-org/build/cng/gitlab-workhorse-ce \
--set gitlab.task-runner.image.repository=registry.gitlab.com/gitlab-org/build/cng/gitlab-task-runner-ce

但是,在使用cert-manager进行http01测试验证域时,安装失败。为此,在运行上面的命令之前,我已经将基本域指向群集中现有的负载均衡器。

成功进行http01验证需要做些其他事情吗?

错误:

Conditions:
Last Transition Time:  2018-11-18T15:22:00Z
Message:               http-01 self check failed for domain "asdsa.asdasd.net"
Reason:                ValidateError
Status:                False
Type:                  Ready

更多信息:

Load Balancer的运行状况检查也一直失败。因此,即使使用自签名证书,安装也会失败。

当尝试ssh进入一个节点并检查返回状态时,这就是我看到的:

$ 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
}

而且,当我检查入口控制器服务时,它已经启动并正在运行:

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

1 个答案:

答案 0 :(得分:1)

问题已在此处解决-https://gitlab.com/charts/gitlab/issues/939

基本上,该线程中提到的解决方案未正式记录,因为它需要确认。