pods from jobs created by kustomization become orphan after kustomization gets deleted

[miadabrin]

When a kustomization object is deleted (with prune: true) the jobs underneath it will be deleted as well but Completed pods belonging to those jobs do not get deleted.

This should have something to do with PropagationPolicy when issuing the delete command from kubeclient as I read through the code ( it should be set to foreground or background ).

reproducing
create a simple kustomization with a job in it, delete the kustomization, you will see the job is deleted but the pod belonging to the job is still there

observations
OwnerReferences are wiped out from the pods when the job is deleted.

Expected behaviour
Pods should be deleted along with jobs when kustomization is deleted.

References

• https://github.com/kubernetes-sigs/controller-runtime/blob/b1efff64d3d2100d701fa1a85b2ba71a8e9c68aa/pkg/client/options.go#L201
• https://kubernetes.io/docs/tasks/administer-cluster/use-cascading-deletion/
• Deleting jobs via the API leaves pods kubernetes/kubernetes#20902

Sidenote
I can probably create a PR for this