Hi, following the gitlab advices to use latest helm charts I’m using following commands to install gitlab-ce
The whole process looks quite ok, after following the procedures for helm installation in my openshift cluster some of the pods don’t come up; especially the postgresql pod does not come up with error “Create Container Config Error” (maybe the reason for the other ones). Any hint what i can do?
My Environment:
kubectl version
Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.1+a0ce1bc657", GitCommit:"a0ce1bc", GitTreeState:"clean", BuildDate:"2018-06-24T01:54:00Z", GoVersion:"go1.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.1+a0ce1bc657", GitCommit:"a0ce1bc", GitTreeState:"clean", BuildDate:"2018-06-24T01:54:00Z", GoVersion:"go1.9", Compiler:"gc", Platform:"linux/amd64"}
[root@ocn01de ~]# oc version
oc v3.9.0+71543b2-33
kubernetes v1.9.1+a0ce1bc657
features: Basic-Auth GSSAPI Kerberos SPNEGO
openshift v3.9.0+71543b2-33
kubernetes v1.9.1+a0ce1bc657
Steps that i made:
helm repo add gitlab https://charts.gitlab.io/
helm repo update
helm upgrade --install gitlab-ce gitlab/gitlab --timeout 600 --set global.hosts.domain=be1.io --set global.hosts.externalIP=207.180.198.115 --set certmanager-issuer.email=martin@be1.io --set global.edition=ce
Console Output:
Release "gitlab-ce" does not exist. Installing it now.
NAME: gitlab-ce
LAST DEPLOYED: Fri Jan 4 17:13:39 2019
NAMESPACE: gitlab-ce
STATUS: DEPLOYED
RESOURCES:
==> v1/ConfigMap
NAME DATA AGE
gitlab-ce-certmanager-issuer-certmanager 2 3s
gitlab-ce-gitlab-runner 3 3s
gitlab-ce-gitaly 3 3s
gitlab-ce-gitlab-shell 2 3s
gitlab-ce-nginx-ingress-tcp 1 3s
gitlab-ce-migrations 4 3s
gitlab-ce-sidekiq-all-in-1 1 3s
gitlab-ce-sidekiq 6 3s
gitlab-ce-task-runner 4 3s
gitlab-ce-unicorn 7 3s
gitlab-ce-workhorse-config 3 3s
gitlab-ce-unicorn-tests 1 3s
gitlab-ce-minio-config-cm 3 3s
gitlab-ce-nginx-ingress-controller 7 3s
gitlab-ce-postgresql 0 3s
gitlab-ce-prometheus-server 3 3s
gitlab-ce-redis 2 3s
gitlab-ce-registry 2 3s
==> v1beta1/CustomResourceDefinition
NAME AGE
certificates.certmanager.k8s.io 3s
clusterissuers.certmanager.k8s.io 3s
issuers.certmanager.k8s.io 3s
==> v1beta1/ClusterRoleBinding
NAME AGE
gitlab-ce-certmanager 3s
gitlab-ce-prometheus-alertmanager 3s
gitlab-ce-prometheus-kube-state-metrics 3s
gitlab-ce-prometheus-node-exporter 3s
gitlab-ce-prometheus-server 3s
==> v1beta1/Role
NAME AGE
gitlab-ce-gitlab-runner 3s
==> v1/Job
NAME COMPLETIONS DURATION AGE
gitlab-ce-issuer.1 0/1 1s 1s
gitlab-ce-migrations.1 0/1 1s 1s
gitlab-ce-minio-create-buckets.1 0/1 1s 1s
==> v2beta1/HorizontalPodAutoscaler
NAME REFERENCE TARGETS MINPODS MAXPODS REPLICAS AGE
gitlab-ce-gitlab-shell Deployment/gitlab-ce-gitlab-shell <unknown>/75% 2 10 0 1s
gitlab-ce-sidekiq-all-in-1 Deployment/gitlab-ce-sidekiq-all-in-1 <unknown>/350m 1 10 0 1s
gitlab-ce-unicorn Deployment/gitlab-ce-unicorn <unknown>/1 2 10 0 1s
gitlab-ce-registry Deployment/gitlab-ce-registry <unknown>/75% 2 10 0 1s
==> v1/PersistentVolumeClaim
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
gitlab-ce-minio Bound vol125 500Gi RWO,RWX 3s
gitlab-ce-postgresql Bound vol183 500Gi RWO,RWX 3s
gitlab-ce-prometheus-server Bound vol62 500Gi RWO,RWX 3s
gitlab-ce-redis Bound vol185 500Gi RWO,RWX 3s
==> v1beta1/ClusterRole
NAME AGE
gitlab-ce-certmanager 3s
gitlab-ce-prometheus-kube-state-metrics 3s
gitlab-ce-prometheus-server 3s
==> v1/Service
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
gitlab-ce-gitaly ClusterIP None <none> 8075/TCP,9236/TCP 3s
gitlab-ce-gitlab-shell ClusterIP 172.30.206.116 <none> 22/TCP 3s
gitlab-ce-unicorn ClusterIP 172.30.148.67 <none> 8080/TCP,8181/TCP 2s
gitlab-ce-minio-svc ClusterIP 172.30.250.77 <none> 9000/TCP 2s
gitlab-ce-nginx-ingress-controller-metrics ClusterIP 172.30.22.173 <none> 9913/TCP 2s
gitlab-ce-nginx-ingress-controller LoadBalancer 172.30.130.110 172.29.244.50,172.29.244.50 80:32476/TCP,443:31965/TCP,22:32468/TCP 2s
gitlab-ce-nginx-ingress-controller-stats ClusterIP 172.30.145.142 <none> 18080/TCP 2s
gitlab-ce-nginx-ingress-default-backend ClusterIP 172.30.107.228 <none> 80/TCP 2s
gitlab-ce-postgresql ClusterIP 172.30.41.84 <none> 5432/TCP 2s
gitlab-ce-prometheus-server ClusterIP 172.30.242.211 <none> 80/TCP 2s
gitlab-ce-redis ClusterIP 172.30.221.6 <none> 6379/TCP,9121/TCP 2s
gitlab-ce-registry ClusterIP 172.30.119.207 <none> 5000/TCP 2s
==> v1beta1/Deployment
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
gitlab-ce-certmanager 1 1 1 0 2s
gitlab-ce-gitlab-runner 1 1 1 0 2s
gitlab-ce-postgresql 1 1 1 0 2s
gitlab-ce-prometheus-server 1 1 1 0 1s
==> v1beta2/StatefulSet
NAME DESIRED CURRENT AGE
gitlab-ce-gitaly 1 1 1s
==> v1/Role
NAME AGE
gitlab-ce-certmanager-issuer 3s
gitlab-ce-nginx-ingress 3s
==> v1beta1/RoleBinding
NAME AGE
gitlab-ce-gitlab-runner 3s
==> v1beta2/Deployment
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
gitlab-ce-gitlab-shell 1 1 1 0 2s
gitlab-ce-sidekiq-all-in-1 1 1 1 0 2s
gitlab-ce-task-runner 1 1 1 0 2s
gitlab-ce-unicorn 1 1 1 0 2s
gitlab-ce-minio 1 1 1 0 2s
gitlab-ce-nginx-ingress-controller 3 0 0 0 2s
gitlab-ce-nginx-ingress-default-backend 2 2 2 0 2s
gitlab-ce-redis 1 1 1 0 1s
gitlab-ce-registry 1 1 1 0 1s
==> v1beta1/PodDisruptionBudget
NAME MIN AVAILABLE MAX UNAVAILABLE ALLOWED DISRUPTIONS AGE
gitlab-ce-gitaly N/A 1 0 3s
gitlab-ce-gitlab-shell N/A 1 0 3s
gitlab-ce-sidekiq N/A 1 0 3s
gitlab-ce-unicorn N/A 1 0 3s
gitlab-ce-minio-v1 N/A 1 0 3s
gitlab-ce-nginx-ingress-controller 2 N/A 0 3s
gitlab-ce-nginx-ingress-default-backend 1 N/A 0 3s
gitlab-ce-redis-v1 N/A 1 0 3s
gitlab-ce-registry-v1 N/A 1 0 3s
==> v1/ServiceAccount
NAME SECRETS AGE
gitlab-ce-certmanager-issuer 2 3s
gitlab-ce-certmanager 2 3s
gitlab-ce-gitlab-runner 2 3s
gitlab-ce-nginx-ingress 2 3s
gitlab-ce-prometheus-alertmanager 2 3s
gitlab-ce-prometheus-kube-state-metrics 2 3s
gitlab-ce-prometheus-node-exporter 2 3s
gitlab-ce-prometheus-server 2 3s
==> v1/RoleBinding
NAME AGE
gitlab-ce-certmanager-issuer 3s
gitlab-ce-nginx-ingress 3s
==> v1beta1/Ingress
NAME HOSTS ADDRESS PORTS AGE
gitlab-ce-unicorn gitlab.be1.io 80, 443 1s
gitlab-ce-minio minio.be1.io 80, 443 1s
gitlab-ce-registry registry.be1.io 80, 443 1s
==> v1/Pod(related)
NAME READY STATUS RESTARTS AGE
gitlab-ce-certmanager-67549bf84c-g8hnn 0/1 ContainerCreating 0 2s
gitlab-ce-gitlab-runner-58c964b556-zjwct 0/1 Init:0/1 0 2s
gitlab-ce-gitlab-shell-7d4c6b7554-m5fq4 0/1 Init:0/2 0 2s
gitlab-ce-sidekiq-all-in-1-5b4844dc6-c4kwn 0/1 Init:0/3 0 2s
gitlab-ce-task-runner-5d7d7cb65f-m8jpj 0/1 Init:0/2 0 2s
gitlab-ce-unicorn-7f4646c448-66f5h 0/2 Pending 0 2s
gitlab-ce-minio-5dd4f85c65-n8bzn 0/1 Pending 0 2s
gitlab-ce-nginx-ingress-default-backend-7955548dbf-9tclb 0/1 Pending 0 1s
gitlab-ce-nginx-ingress-default-backend-7955548dbf-xm4wc 0/1 ContainerCreating 0 2s
gitlab-ce-postgresql-cc95bcc7b-mk6s4 0/2 Pending 0 1s
gitlab-ce-prometheus-server-58d77dcbc7-5bq44 0/2 Pending 0 1s
gitlab-ce-redis-5dc6554754-g62zc 0/2 Pending 0 1s
gitlab-ce-registry-856449f5db-5khf9 0/1 Pending 0 1s
gitlab-ce-gitaly-0 0/1 Pending 0 1s
gitlab-ce-issuer.1-gxqbv 0/1 Pending 0 1s
gitlab-ce-migrations.1-8cn8n 0/1 Pending 0 1s
gitlab-ce-minio-create-buckets.1-nh2wm 0/1 Pending 0 1s
svc/gitlab-ce-postgresql - 172.30.41.84:5432 -> postgresql
deployment/gitlab-ce-postgresql deploys postgres:9.6.8,wrouesnel/postgres_exporter:v0.1.1
deployment #1 running for 16 minutes - 0/1 pods
No Errors, The Result is that some of the pods start ok, others fail - especially the postgresql pod:
Container gitlab-ce-postgresql
State:
Waiting (CreateContainerConfigError)
Ready:
false
Restart Count:
0
- corrected and that fixed the issue for about 80% of the containers.