Skip to content

Some K8S resources do not get deleted after 'helm delete'. #101

@erenatas

Description

@erenatas

Hello,

I would like to report an issue (I believe). After trying to delete the deployed helm chart, I can see that there are job pods remained. Here is an example of kubectl get po after helm delete --purge stackstorm on Helm 2 or helm delete stackstorm on Helm 3:

❯ kubectl get po   
NAME                                                              READY   STATUS                       RESTARTS   AGE
stackstorm-job-st2-apikey-load-j8rkv                              0/1     Completed                    0          6d21h
stackstorm-job-st2-key-load-wbdxp                                 0/1     Completed                    0          6d21h
stackstorm-job-st2-register-content-l6rmh                         0/1     Completed                    0          6d21h

Not only these pods, but also the jobs remain as well. on kubectl get jobs, I can see:

❯ kubectl get job
NAME                                   COMPLETIONS   DURATION   AGE
stackstorm-job-st2-apikey-load         1/1           45s        6d21h
stackstorm-job-st2-key-load            1/1           9s         6d21h
stackstorm-job-st2-register-content    1/1           25s        6d21h

There are also PV,PVC objects remained but I believe that is desired?

Thanks!

Edit: I believe that the reason is related to this. I think both jobs and pods should be deleted on helm delete and also, at least, pods of jobs should be deleted after they have been successful.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions