helm: helm reset --force reports OK but tiller is not deleted

We want to be able to do helm init --upgrade in a manual gitlab-ci stage helm init suceeded but didn’t do anything, so I added helm reset --force followed with helm init, again, nothing happened

when I do helm reset --force from my terminal and run the manual stage with helm init, everything works as expected, so the helm context in the pipeline is definitely set right.

$ 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:"10", GitVersion:"v1.10.7", GitCommit:"0c38c362511b20a098d7cd855f1314dad92c2780", GitTreeState:"clean", BuildDate:"2018-08-20T10:09:03Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"10+", GitVersion:"v1.10.7-gke.2", GitCommit:"8d9503f982872112eb283f78cefc6944af640427", GitTreeState:"clean", BuildDate:"2018-09-13T22:19:55Z", GoVersion:"go1.9.3b4", Compiler:"gc", Platform:"linux/amd64"}
$ echo "$HELM_HOME"

$ kubectl get pods -n kube-system | grep tiller
tiller-deploy-674ff75566-r5658                          1/1       Running   0          27m
$ helm reset --force
Tiller (the Helm server-side component) has been uninstalled from your Kubernetes Cluster.
$ kubectl get pods -n kube-system | grep tiller
tiller-deploy-674ff75566-r5658                          1/1       Running   0          27m

how is this still running when I get " Tiller has been uninstalled"?

Cloud Provider/Platform: GKE

About this issue

Original URL
State: closed
Created 6 years ago
Reactions: 2
Comments: 20 (7 by maintainers)

Most upvoted comments

I am seeing the same bug with helm 2.12.2 and GKE k8s 1.11.5-gke.5. Before helm reset --force:

$ k get all --namespace=helm
NAME                                READY     STATUS    RESTARTS   AGE
po/tiller-deploy-5f55c9bb7b-mppnb   1/1       Running   0          4m

NAME                TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)     AGE
svc/tiller-deploy   ClusterIP   10.113.7.182   <none>        44134/TCP   4m

NAME                   AGE
deploy/tiller-deploy   4m

NAME                          AGE
rs/tiller-deploy-5f55c9bb7b   4m

After helm reset --force and “Tiller (the Helm server-side component) has been uninstalled from your Kubernetes Cluster.”

$ k get all --namespace=helm
NAME                                READY     STATUS    RESTARTS   AGE
po/tiller-deploy-5f55c9bb7b-mppnb   1/1       Running   0          4m

NAME                          AGE
rs/tiller-deploy-5f55c9bb7b   4m

Only the Service and Deployment are deleted. When deleting the Deployment, cascade delete appears to have been disabled when helm deleted the Deployment.

If I delete the deployment myself with kubectl is works just fine

$ k --namespace=helm delete service tiller-deploy
service "tiller-deploy" deleted
$ k --namespace=helm delete deployment tiller-deploy
deployment "tiller-deploy" deleted
$ k get all --namespace=helm
No resources found.

So it appear helm is doing something that actually disable cascade delete, the equivalent of:

$ k --namespace=helm delete deployment tiller-deploy --cascade=false

'helm resetworks just like–cascade=false` is set:

$ k get all --namespace=helm
NAME                                READY     STATUS    RESTARTS   AGE
po/tiller-deploy-5f55c9bb7b-pw9lb   1/1       Running   0          45s

NAME                TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)     AGE
svc/tiller-deploy   ClusterIP   10.113.12.46   <none>        44134/TCP   45s

NAME                   AGE
deploy/tiller-deploy   45s

NAME                          AGE
rs/tiller-deploy-5f55c9bb7b   45s
$ k --namespace=helm delete deployment tiller-deploy --cascade=false
deployment "tiller-deploy" deleted
$ k get all --namespace=helm
NAME                                READY     STATUS    RESTARTS   AGE
po/tiller-deploy-5f55c9bb7b-pw9lb   1/1       Running   0          1m

NAME                TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)     AGE
svc/tiller-deploy   ClusterIP   10.113.12.46   <none>        44134/TCP   1m

NAME                          AGE
rs/tiller-deploy-5f55c9bb7b   1m

whereisaaron on Dec 29, 2018