helm version[apps@mvxl1484 ~]$ helm versionClient: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"}Error: could not find tiller

docker search tiller[apps@mvxl1484 k8s]$ docker search tillerNAME DESCRIPTION STARS OFFICIAL AUTOMATEDsapcc/tiller Mirror of https://gcr.io/kubernetes-helm/t... 5 jessestuart/tiller Nightly multi-architecture (amd64, arm64, ... 4 [OK]ist0ne/tiller https://gcr.io/kubernetes-helm/tiller 3 [OK]timotto/rpi-tiller k8s.io/tiller for Raspberry Pi 1 itinerisltd/tiller 1 rancher/tiller 1 luxas/tiller 1 ibmcom/tiller Docker Image for IBM Cloud private-CE (Com... 1 ansibleplaybookbundle/tiller-apb An APB that deploys tiller for use with helm. 0 [OK]pcanham/tiller tiller image for Raspberry Pi for testing ... 0 kubeapps/tiller-proxy 0 appscode/tiller 0 jmgao1983/tiller from gcr.io/kubernetes-helm/tiller 0 [OK]anjia0532/tiller 0 4admin2root/tiller gcr.io/kubernetes-helm/tiller 0 [OK]ibmcom/tiller-ppc64le Docker Image for IBM Cloud Private-CE (Com... 0 szgrgo/helm-with-tiller Use helm and tiller together 0 [OK]关注第一行：Mirror of https://gcr.io/kubernetes-helm/t...因为gcr.io库的封锁，用这个镜像。

cat tiller.yaml ---apiVersion: v1kind: ServiceAccountmetadata: ?name: tiller ?namespace: kube-system---apiVersion: rbac.authorization.k8s.io/v1beta1kind: ClusterRoleBindingmetadata: ?name: tillerroleRef: ?apiGroup: rbac.authorization.k8s.io ?kind: ClusterRole ?name: cluster-adminsubjects: ?- kind: ServiceAccount ???name: tiller ???namespace: kube-system[root@compass-user-hd-master3]:~# 

kubectl apply -f tiller.yaml

[apps@mvxl1484 k8s]$ helm versionClient: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"}Error: could not find a ready tiller pod

[apps@mvxl1484 k8s]$ kubectl get pod --all-namespacesNAMESPACE NAME READY STATUS RESTARTS AGE3dkube-system kubernetes-dashboard-58f5cb49c-zf7cn 1/1 Running 0 2dkube-system tiller-deploy-9bdb7c6bc-28rv6 0/1 ImagePullBackOff 0 42s

[apps@mvxl1484 k8s]$ kubectl describe pod tiller-deploy-9bdb7c6bc-28rv6 -n kube-systemName: tiller-deploy-9bdb7c6bc-28rv6Namespace: kube-systemNode: mvxl2655/10.16.91.120Start Time: Thu, 22 Nov 2018 18:00:01 +0800Labels: app=helmname=tillerpod-template-hash=568637267Annotations: <none>Status: PendingIP: 10.16.3.18Controlled By: ReplicaSet/tiller-deploy-9bdb7c6bcContainers:tiller:Container ID: Image: gcr.io/kubernetes-helm/tiller:v2.11.0Image ID: Ports: 44134/TCP, 44135/TCPState: WaitingReason: ImagePullBackOffReady: FalseRestart Count: 0Liveness: http-get http://:44135/liveness delay=1s timeout=1s period=10s #success=1 #failure=3Readiness: http-get http://:44135/readiness delay=1s timeout=1s period=10s #success=1 #failure=3Environment:TILLER_NAMESPACE: kube-systemTILLER_HISTORY_MAX: 0Mounts:/var/run/secrets/kubernetes.io/serviceaccount from tiller-token-ls9t2 (ro)Conditions:Type StatusInitialized True Ready False PodScheduled True Volumes:tiller-token-ls9t2:Type: Secret (a volume populated by a Secret)SecretName: tiller-token-ls9t2Optional: falseQoS Class: BestEffortNode-Selectors: <none>Tolerations: node.kubernetes.io/not-ready:NoExecute for 300snode.kubernetes.io/unreachable:NoExecute for 300sEvents:Type Reason Age From Message---- ------ ---- ---- -------Normal Scheduled 1m default-scheduler Successfully assigned tiller-deploy-9bdb7c6bc-28rv6 to mvxl2655Normal SuccessfulMountVolume 1m kubelet, mvxl2655 MountVolume.SetUp succeeded for volume "tiller-token-ls9t2"Normal Pulling 1m (x2 over 1m) kubelet, mvxl2655 pulling image "gcr.io/kubernetes-helm/tiller:v2.11.0"Warning Failed 55s (x2 over 1m) kubelet, mvxl2655 Failed to pull image "gcr.io/kubernetes-helm/tiller:v2.11.0": 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 55s (x2 over 1m) kubelet, mvxl2655 Error: ErrImagePullWarning Failed 50s (x5 over 1m) kubelet, mvxl2655 Error: ImagePullBackOffNormal SandboxChanged 49s (x7 over 1m) kubelet, mvxl2655 Pod sandbox changed, it will be killed and re-created.Normal BackOff 47s (x6 over 1m) kubelet, mvxl2655 Back-off pulling image "gcr.io/kubernetes-helm/tiller:v2.11.0"最后一行代表镜像拉取失败：Back-off pulling image "gcr.io/kubernetes-helm/tiller:v2.11.0"

[apps@mvxl1484 k8s]$ kubectl edit deploy tiller-deploy -n kube-systemapiVersion: extensions/v1beta1kind: Deploymentmetadata:annotations:deployment.kubernetes.io/revision: "2"creationTimestamp: 2018-11-22T10:00:00Zgeneration: 2labels: app: helmname: tillername: tiller-deploynamespace: kube-systemresourceVersion: "398202"selfLink: /apis/extensions/v1beta1/namespaces/kube-system/deployments/tiller-deployuid: 5fd7370d-ee3d-11e8-a632-0050568a39f2spec:replicas: 1selector:matchLabels:app: helmname: tillerstrategy:rollingUpdate:maxSurge: 1maxUnavailable: 1type: RollingUpdatetemplate:metadata:creationTimestamp: nulllabels:app: helmname: tillerspec:automountServiceAccountToken: truecontainers:- env:- name: TILLER_NAMESPACEvalue: kube-system- name: TILLER_HISTORY_MAXvalue: "0"image: sapcc/tiller:v2.11.0imagePullPolicy: IfNotPresent将 image ?gcr.io/kubernetes-helm/tiller:v2.11.0 ?替换成 ??image: sapcc/tiller:v2.11.0

[apps@mvxl1484 k8s]$ kubectl get pod -n kube-systemtiller-deploy-6b84d85487-4h272 1/1 Running 0 45s

[apps@mvxl1484 k8s]$ helm versionClient: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"}Server: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b