helm Error: could not find a ready tiller pod

An error is reported when using helm in docker for windows. The reason is that the image pull of tiller fails. The processing methods are as follows:
1. View the tiller-deploy-xxx container name: kubectl get pods --namespace kube-system
2. View details: kubectl --namespace kube-system describe pod tiller-deploy-7d6dbd958-sb92l

You can see the error content:

  Normal   Scheduled  22m                   default-scheduler        Successfully assigned kube-system/tiller-deploy-7d6dbd958-sb92l to docker-desktop
  Normal   Pulling    20m (x4 over 22m)     kubelet, docker-desktop  Pulling image "gcr.io/kubernetes-helm/tiller:v2.16.6"
  Warning  Failed     19m (x4 over 22m)     kubelet, docker-desktop  Failed to pull image "gcr.io/kubernetes-helm/tiller:v2.16.6": rpc error: code = Unknown desc = Error response from daemon: Get https://gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
  Warning  Failed     19m (x4 over 22m)     kubelet, docker-desktop  Error: ErrImagePull
  Normal   BackOff    17m (x15 over 22m)    kubelet, docker-desktop  Back-off pulling image "gcr.io/kubernetes-helm/tiller:v2.16.6"
  Warning  Failed     7m10s (x56 over 22m)  kubelet, docker-desktop  Error: ImagePullBackOff

3. Rename the image through Alibaba Cloud pull

docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/tiller:v2.16.6
docker tag registry.cn-hangzhou.aliyuncs.com/google_containers/tiller:v2.16.6 gcr.io/kubernetes-helm/tiller:v2.16.6 
docker rmi registry.cn-hangzhou.aliyuncs.com/google_containers/tiller:v2.16.6 

4. Restart the container tiller-deploy-xxx

Guess you like

Origin www.cnblogs.com/wswind/p/12703279.html