Can't initialize helm on Microk8s, tiller image not being pulled due to errors

General Discussions microk8s
1

I am using Microk8s and after performing microk8s enable helm helm3 I did microk8s helm init so it could initialize and after that I would be able to install some helm charts I need for my application.

The init does not perform because the tiller pod keeps getting an error when performing the image pull, here is the configuration for that pod:

mk -n kube-system describe pod tiller-deploy-7f9796b596-9lqdq
Name:         tiller-deploy-7f9796b596-9lqdq
Namespace:    kube-system
Priority:     0
Node:         macprokiller/192.168.1.132
Start Time:   Fri, 24 Sep 2021 18:27:08 +0100
Labels:       app=helm
              name=tiller
              pod-template-hash=7f9796b596
Annotations:  cni.projectcalico.org/podIP: 10.1.107.76/32
              cni.projectcalico.org/podIPs: 10.1.107.76/32
Status:       Pending
IP:           10.1.107.76
IPs:
  IP:           10.1.107.76
Controlled By:  ReplicaSet/tiller-deploy-7f9796b596
Containers:
  tiller:
    Container ID:   
    Image:          gcr.io/kubernetes-helm/tiller:v2.16.7
    Image ID:       
    Ports:          44134/TCP, 44135/TCP
    Host Ports:     0/TCP, 0/TCP
    State:          Waiting
      Reason:       ImagePullBackOff
    Ready:          False
    Restart Count:  0
    Liveness:       http-get http://:44135/liveness delay=1s timeout=1s period=10s #success=1 #failure=3
    Readiness:      http-get http://:44135/readiness delay=1s timeout=1s period=10s #success=1 #failure=3
    Environment:
      TILLER_NAMESPACE:    kube-system
      TILLER_HISTORY_MAX:  0
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-58kkc (ro)
Conditions:
  Type              Status
  Initialized       True 
  Ready             False 
  ContainersReady   False 
  PodScheduled      True 
Volumes:
  kube-api-access-58kkc:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason     Age                   From               Message
  ----     ------     ----                  ----               -------
  Normal   Scheduled  6m9s                  default-scheduler  Successfully assigned kube-system/tiller-deploy-7f9796b596-9lqdq to macprokiller
  Normal   Pulling    4m52s (x4 over 6m9s)  kubelet            Pulling image "gcr.io/kubernetes-helm/tiller:v2.16.7"
  Warning  Failed     4m52s (x4 over 6m9s)  kubelet            Failed to pull image "gcr.io/kubernetes-helm/tiller:v2.16.7": rpc error: code = Unknown desc = failed to pull and unpack image "gcr.io/kubernetes-helm/tiller:v2.16.7": failed to resolve reference "gcr.io/kubernetes-helm/tiller:v2.16.7": failed to authorize: failed to fetch anonymous token: unexpected status: 401 Unauthorized
  Warning  Failed     4m52s (x4 over 6m9s)  kubelet            Error: ErrImagePull
  Warning  Failed     4m37s (x6 over 6m9s)  kubelet            Error: ImagePullBackOff
  Normal   BackOff    60s (x22 over 6m9s)   kubelet            Back-off pulling image "gcr.io/kubernetes-helm/tiller:v2.16.7"

Can anyone help me out here?

2

Do you still need helm2? I don’t think that tiller image is still in that registry.
Helm2 is no longer supported.

3

Did you get the answer ? I have same issue with tiller.
"
Failed to pull image “Google Cloud console”: rpc error: code = Unknown desc = failed to pull and unpack image “Google Cloud console”: failed to resolve reference “Google Cloud console”: pulling from host gcr.io failed with status code [manifests v2.16.7]: 400 Bad Request
"

4

I just installed helm3 and it installed tiller. Don’t install helm2. microk8s enable helm3