tiller-deploy is in status CrashLoopBackOff

[Eric-Zhang1990]

@Tomcli If tiller-deploy is in status CrashLoopBackOff, not in running, but I run tiller manually, and after I run "helm install .", some pods are also on status CrashLoopBackOff, so I wander if tiller-deploy affect the installation of FfDL???
Thank you very much.

[Tomcli]

Hi @Eric-Zhang1990, Tiller is the helm server which is responsible for properly deploying the FfDL helm chart. Can you check which version of Helm you are using? helm version and log the errors from the tiller pod? kubectl logs tiller-deploy-fffbc59d4-qkhfb -n kube-system.

Thank you.

[Eric-Zhang1990]

@Tomcli Thank you for kind reply, after I delete it and it started by itself, it is in status running. Log is following.

Note: Tiller is started manually.
$helm version
Client: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"}

$kubectl version
Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.4", GitCommit:"f49fa022dbe63faafd0da106ef7e05a29721d3f1", GitTreeState:"clean", BuildDate:"2018-12-14T07:10:00Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.4", GitCommit:"f49fa022dbe63faafd0da106ef7e05a29721d3f1", GitTreeState:"clean", BuildDate:"2018-12-14T06:59:37Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}

$kubectl logs tiller-deploy-fffbc59d4-7vkt5 -n kube-system
[main] 2019/01/21 11:40:50 Starting Tiller v2.11.0 (tls=true)
[main] 2019/01/21 11:40:50 GRPC listening on :44134
[main] 2019/01/21 11:40:50 Probes listening on :44135
[main] 2019/01/21 11:40:50 Storage driver is ConfigMap
[main] 2019/01/21 11:40:50 Max history per release is 0