Unable to install Ingress (and therefore JupyterHub)


As the integration of Jupyterhub and Gitlab seems so seamless using Jupyterhub as a managed app, I wanted to give it a go.

:white_check_mark: Install gitlab docker image
:white_check_mark: Figured out that a kubernete node is needed to power Gitlab’s managed apps
:white_check_mark: Install minikube on the machine
:white_check_mark: Add the existing cluster
:x: Jupyterhub grayed out
:white_check_mark: Install Prometheus
:x:Install Ingress
:x:Install Jupyterhub

And I can’t figure out how to debug the ingress pod, is there any workaround or any mean to have an output more detailed ?

kubectl get pods
NAME                                            READY   STATUS    RESTARTS   AGE
install-ingress                                 0/1     Error     0          13m
prometheus-kube-state-metrics-6b5764b4-qnt5x    1/1     Running   0          27m
prometheus-prometheus-server-7d499465c7-4zs57   2/2     Running   0          27m

kubectl describe pods install-ingress
Name:         install-ingress
Namespace:    gitlab-managed-apps
Priority:     0
Node:         minikube/
Start Time:   Sun, 23 Aug 2020 12:30:00 +0200
Labels:       gitlab.org/action=install
Annotations:  <none>
Status:       Failed
    Container ID:  docker://8bd9229a4683dbf38b153792927b9c1377266949da47ee9f179cb8b016dc088c
    Image:         registry.gitlab.com/gitlab-org/cluster-integration/helm-install-image/releases/2.16.9-kube-1.13.12
    Image ID:      docker-pullable://registry.gitlab.com/gitlab-org/cluster-integration/helm-install-image/releases/2.16.9-kube-1.13.12@sha256:bcbbb7a1d9b5617af7ab18f66542c86a153b9fef387014467390f6ea9bb4f1b1
    Port:          <none>
    Host Port:     <none>
    State:          Terminated
      Reason:       Error
      Exit Code:    1
      Started:      Sun, 23 Aug 2020 12:30:05 +0200
      Finished:     Sun, 23 Aug 2020 12:35:20 +0200
    Ready:          False
    Restart Count:  0
      HELM_VERSION:      2.16.9
      TILLER_NAMESPACE:  gitlab-managed-apps
      COMMAND_SCRIPT:    set -xeo pipefail
                         export HELM_HOST="localhost:44134"
                         tiller -listen ${HELM_HOST} -alsologtostderr &
                         helm init --client-only
                         helm repo update
                         helm upgrade ingress stable/nginx-ingress --install --atomic --cleanup-on-fail --reset-values --version 1.29.7 --set rbac.create\=true,rbac.enabled\=true --namespace gitlab-managed-apps -f /data/helm/ingress/config/values.yaml
      /data/helm/ingress/config from configuration-volume (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from tiller-token-9v2x5 (ro)
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      values-content-configuration-ingress
    Optional:  false
    Type:        Secret (a volume populated by a Secret)
    SecretName:  tiller-token-9v2x5
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
  Type    Reason     Age    From               Message
  ----    ------     ----   ----               -------
  Normal  Scheduled  6m22s  default-scheduler  Successfully assigned gitlab-managed-apps/install-ingress to minikube
  Normal  Pulling    6m20s  kubelet, minikube  Pulling image "registry.gitlab.com/gitlab-org/cluster-integration/helm-install-image/releases/2.16.9-kube-1.13.12"
  Normal  Pulled     6m18s  kubelet, minikube  Successfully pulled image "registry.gitlab.com/gitlab-org/cluster-integration/helm-install-image/releases/2.16.9-kube-1.13.12"
  Normal  Created    6m18s  kubelet, minikube  Created container helm
  Normal  Started    6m17s  kubelet, minikube  Started container helm

Thanks kindly for your answers, I’m kinda stuck here

MAJ (5h later) : tried to install gitlab via the helm chart, made new profile in my minikube and manually executed minikube addons enable ingress, fails cf issue#8756 in minikube. That may be related

1 Like

Post you install logs (during installation): kubectl logs pod/install-ingress-nginx -n gitlab-managed-apps

I had the same problem. For bare-metalal installation use MetalLB: https://metallb.universe.tf/installation/ https://metallb.universe.tf/configuration/

You can use helm: https://github.com/bitnami/charts/tree/master/bitnami/metallb then you have to change namespace and name:

apiVersion: v1
kind: ConfigMap
  namespace: default
  name: metallb
  config: |
      - addresses:
        name: default
        protocol: layer2

You need get External IP for service/ingress-nginx-ingress-controller:

kubectl get svc --all-namespaces

More about Load Balancing support: https://rancher.com/docs/rancher/v2.x/en/k8s-in-rancher/load-balancers-and-ingress/load-balancers/

Hey CSRedhat,
Early september I fell back to a distinct gitlab/jupyterhub install linked via the plugin.

I must thanks you for your answer, I no longer have my logs but I ended up with the feeling that all my troubles came from bare-metal considerations. Funny thing that you link rancher’s website, for my last try I switched from minikube to k3s.