Impossible to install ingress with Helm tiller

Hello,

It's currently impossible to setup ingress on a fresh kubernetes cluster.

I use gitlab.com

All pods are alive, but i think the ingress default backend is badly configured:

Name:         ingress-nginx-ingress-default-backend-7d66f58f5f-rm6lc
Namespace:    gitlab-managed-apps
Priority:     0
Node:         node2/172.16.10.2
Start Time:   Mon, 13 Apr 2020 16:22:17 +0200
Labels:       app=nginx-ingress
              component=default-backend
              pod-template-hash=7d66f58f5f
              release=ingress
Annotations:  <none>
Status:       Running
IP:           10.233.96.42
IPs:
  IP:           10.233.96.42
Controlled By:  ReplicaSet/ingress-nginx-ingress-default-backend-7d66f58f5f
Containers:
  nginx-ingress-default-backend:
    Container ID:   docker://08760e4dc86eb063d6342061999c060e1562a7e549763cc89ba23cf23d2cd5d6
    Image:          k8s.gcr.io/defaultbackend-amd64:1.5
    Image ID:       docker-pullable://k8s.gcr.io/defaultbackend-amd64@sha256:4dc5e07c8ca4e23bddb3153737d7b8c556e5fb2f29c4558b7cd6e6df99c512c7
    Port:           8080/TCP
    Host Port:      0/TCP
    State:          Running
      Started:      Mon, 13 Apr 2020 16:22:20 +0200
    Ready:          True
    Restart Count:  0
    Liveness:       http-get http://:8080/healthz delay=30s timeout=5s period=10s #success=1 #failure=3
    Readiness:      http-get http://:8080/healthz delay=0s timeout=5s period=5s #success=1 #failure=6
    Environment:    <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from ingress-nginx-ingress-backend-token-57k97 (ro)
Conditions:
  Type              Status
  Initialized       True 
  Ready             True 
  ContainersReady   True 
  PodScheduled      True 
Volumes:
  ingress-nginx-ingress-backend-token-57k97:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  ingress-nginx-ingress-backend-token-57k97
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type    Reason     Age   From               Message
  ----    ------     ----  ----               -------
  Normal  Scheduled  25s   default-scheduler  Successfully assigned gitlab-managed-apps/ingress-nginx-ingress-default-backend-7d66f58f5f-rm6lc to node2
  Normal  Pulled     23s   kubelet, node2     Container image "k8s.gcr.io/defaultbackend-amd64:1.5" already present on machine
  Normal  Created    23s   kubelet, node2     Created container nginx-ingress-default-backend
  Normal  Started    22s   kubelet, node2     Started container nginx-ingress-default-backend

It's seems to be due to this:

    Liveness:       http-get http://:8080/healthz delay=30s timeout=5s period=10s #success=1 #failure=3
    Readiness:      http-get http://:8080/healthz delay=0s timeout=5s period=5s #success=1 #failure=6

Do you have any idea to solve this problem ?

Here is the log of the installer

+ helm init --upgrade
Creating /root/.helm 
Creating /root/.helm/repository 
Creating /root/.helm/repository/cache 
Creating /root/.helm/repository/local 
Creating /root/.helm/plugins 
Creating /root/.helm/starters 
Creating /root/.helm/cache/archive 
Creating /root/.helm/repository/repositories.yaml 
Adding stable repo with URL: https://kubernetes-charts.storage.googleapis.com 
Adding local repo with URL: http://127.0.0.1:8879/charts 
$HELM_HOME has been configured at /root/.helm.

Tiller (the Helm server-side component) has been updated to gcr.io/kubernetes-helm/tiller:v2.16.3 .
+ seq 1 30
+ helm version --tls --tls-ca-cert /data/helm/ingress/config/ca.pem --tls-cert /data/helm/ingress/config/cert.pem --tls-key /data/helm/ingress/config/key.pem
Client: &version.Version{SemVer:"v2.16.3", GitCommit:"1ee0254c86d4ed6887327dabed7aa7da29d7eb0d", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.16.3", GitCommit:"1ee0254c86d4ed6887327dabed7aa7da29d7eb0d", GitTreeState:"clean"}
+ s=0
+ break
+ exit 0
+ helm repo update
Hang tight while we grab the latest from your chart repositories...
...Skip local chart repository
...Successfully got an update from the "stable" chart repository
Update Complete.
+ helm upgrade ingress stable/nginx-ingress --install --atomic --cleanup-on-fail --reset-values --tls --tls-ca-cert /data/helm/ingress/config/ca.pem --tls-cert /data/helm/ingress/config/cert.pem --tls-key /data/helm/ingress/config/key.pem --version 1.29.7 --set 'rbac.create=true,rbac.enabled=true' --namespace gitlab-managed-apps -f /data/helm/ingress/config/values.yaml
Release "ingress" does not exist. Installing it now.
INSTALL FAILED
PURGING CHART
Error: release ingress failed: timed out waiting for the condition
Successfully purged a chart!
Error: release ingress failed: timed out waiting for the condition