Page MenuHomePhabricator

Packaged helm points to non-existent tiller
Closed, InvalidPublic


Trying out the helm version (2.8.1-1) in stretch-wikimedia/main I can't seem to get it running. I think it's using an incorrect Tiller url:

thcipriani@integration-slave-k8s-1013:~$ apt-cache policy helm                                                                                                           
  Installed: 2.8.1-1
  Candidate: 2.8.1-1
  Version table:
 *** 2.8.1-1 1001
       1001 stretch-wikimedia/main amd64 Packages
        100 /var/lib/dpkg/status
thcipriani@integration-slave-k8s-1013:~$ helm init --dry-run --debug | grep -i gcr                                                                                       
thcipriani@integration-slave-k8s-1013:~$ sudo docker pull                                                                             
Error response from daemon: manifest for not found

Trying ^ with the binary release off of github I get:

thcipriani@integration-slave-k8s-1013:~/linux-amd64$ ./helm init --dry-run --debug |
 grep -i gcr                                      
thcipriani@integration-slave-k8s-1013:~$ sudo docker pull                                                                           
v2.8.1: Pulling from kubernetes-helm/tiller                                                                                                                              
Digest: sha256:394fb7d5f2fbaca54f6a0dec387cef926f6ae359786c89f7da67db173b97a322                                                                                          
Status: Image is up to date for

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptMar 23 2018, 10:34 PM
hashar added a subscriber: hashar.Mar 23 2018, 10:46 PM

dockerd in journalctl spurts:

msg="Attempting next endpoint for pull after error: manifest unknown: Failed to fetch \"v2.8\" from request \"/v2/kubernetes-helm/tiller/manifests/v2.8\"."

Your examples list v2.8 vs v2.8.1 ? I guess the Debian package is wrong :(

akosiaris added a comment.EditedMar 23 2018, 11:03 PM

Just pass --tiller-image=docker-registry.discovery.wmnet/tiller:latest to helm init. Alternatively from labs it would be

I had a deeper look. The original build process uses to do the work of figuring out the version. We don't use that in the debian package we ship and our package has version v2.8+unreleased. I am not sure we need to go down the road of actually using during our built and if that actually adds value given that we intend to use our own compatible tiller image

thcipriani closed this task as Invalid.Apr 23 2018, 4:32 PM

Workaround for this seems to work fine, thanks!