Helm Tiller fails to install

Summary

Hi,

I'm adding my own cluster to my project and tiller fails to install.

Steps to reproduce

Setup own cluster (per https://gitlab.com/help/user/project/clusters/index.md#add-existing-kubernetes-cluster)

What is the current bug behavior?

After clicking install I see:

Something went wrong while installing Helm Tiller

Operation failed. Check pod logs for install-helm for more details.

What is the expected correct behavior?

It should install

Relevant logs and/or screenshots

Here are the pod details:

kubectl get pods --all-namespaces 
NAMESPACE             NAME                             READY   STATUS    RESTARTS   AGE
gitlab-managed-apps   install-helm                     0/1     Error     0          6s
kube-system           coredns-5644d7b6d9-d9f89         1/1     Running   0          65m
kube-system           coredns-5644d7b6d9-n5j2c         1/1     Running   0          65m
kube-system           etcd-k8sone                      1/1     Running   1          64m
kube-system           kube-apiserver-k8sone            1/1     Running   1          64m
kube-system           kube-controller-manager-k8sone   1/1     Running   1          64m
kube-system           kube-flannel-ds-amd64-424f7      1/1     Running   1          64m
kube-system           kube-proxy-x7jvr                 1/1     Running   1          65m
kube-system           kube-scheduler-k8sone            1/1     Running   1          64m

And pod description:

kubectl describe pod install-helm --namespace gitlab-managed-apps
Name:         install-helm
Namespace:    gitlab-managed-apps
Priority:     0
Node:         k8sone/192.168.1.50
Start Time:   Thu, 26 Sep 2019 20:41:25 +0000
Labels:       gitlab.org/action=install
              gitlab.org/application=helm
Annotations:  <none>
Status:       Failed
IP:           10.244.0.9
IPs:
  IP:  10.244.0.9
Containers:
  helm:
    Container ID:  docker://e9700334a23aff6ddb5c2eaeca310aafb4a4deb51d2a56cb698785d3aa0d98e8
    Image:         registry.gitlab.com/gitlab-org/cluster-integration/helm-install-image/releases/2.14.3-kube-1.11.10
    Image ID:      docker-pullable://registry.gitlab.com/gitlab-org/cluster-integration/helm-install-image/releases/2.14.3-kube-1.11.10@sha256:08873320d6c12f347bdec9656bd7f6b1193df53495ea5b9028663c68965a4c1a
    Port:          <none>
    Host Port:     <none>
    Command:
      /bin/sh
    Args:
      -c
      $(COMMAND_SCRIPT)
    State:          Terminated
      Reason:       Error
      Exit Code:    1
      Started:      Thu, 26 Sep 2019 20:41:28 +0000
      Finished:     Thu, 26 Sep 2019 20:41:30 +0000
    Ready:          False
    Restart Count:  0
    Environment:
      HELM_VERSION:      2.14.3
      TILLER_NAMESPACE:  gitlab-managed-apps
      COMMAND_SCRIPT:    set -xeo pipefail
                         helm init --tiller-tls --tiller-tls-verify --tls-ca-cert /data/helm/helm/config/ca.pem --tiller-tls-cert /data/helm/helm/config/cert.pem --tiller-tls-key /data/helm/helm/config/key.pem --service-account tiller
    Mounts:
      /data/helm/helm/config from configuration-volume (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from tiller-token-hml27 (ro)
Conditions:
  Type              Status
  Initialized       True 
  Ready             False 
  ContainersReady   False 
  PodScheduled      True 
Volumes:
  configuration-volume:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      values-content-configuration-helm
    Optional:  false
  tiller-token-hml27:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  tiller-token-hml27
    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  <unknown>  default-scheduler  Successfully assigned gitlab-managed-apps/install-helm to k8sone
  Normal  Pulling    5m5s       kubelet, k8sone    Pulling image "registry.gitlab.com/gitlab-org/cluster-integration/helm-install-image/releases/2.14.3-kube-1.11.10"
  Normal  Pulled     5m5s       kubelet, k8sone    Successfully pulled image "registry.gitlab.com/gitlab-org/cluster-integration/helm-install-image/releases/2.14.3-kube-1.11.10"
  Normal  Created    5m4s       kubelet, k8sone    Created container helm
  Normal  Started    5m4s       kubelet, k8sone    Started container helm

pod logs:

kubectl logs install-helm --namespace gitlab-managed-apps 
+ helm init --tiller-tls --tiller-tls-verify --tls-ca-cert /data/helm/helm/config/ca.pem --tiller-tls-cert /data/helm/helm/config/cert.pem --tiller-tls-key /data/helm/helm/config/key.pem --service-account tiller
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.
Error: error installing: the server could not find the requested resource

Kubernetes version:

kubectl version 
Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.0", GitCommit:"2bd9643cee5b3b3a5ecbd3af49d09018f0773c77", GitTreeState:"clean", BuildDate:"2019-09-18T14:36:53Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.0", GitCommit:"2bd9643cee5b3b3a5ecbd3af49d09018f0773c77", GitTreeState:"clean", BuildDate:"2019-09-18T14:27:17Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}

Output of checks

This bug happens on GitLab.com