-
Notifications
You must be signed in to change notification settings - Fork 39.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update kubectl to use PropagationPolicy instead of OrphanDependents #46659
Comments
Issues go stale after 90d of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or |
Job deletion hanging on kubernetes 1.8, because job appeared in jobs list after successful deletion request. * All related job's pods are deleted explicitly now. * Job deletion request is now being done with parameter orphanDependents=false. Also: * According to the docs: https://kubernetes.io/docs/concepts/workloads/controllers/garbage-collection/, orphanDependents is deprecated, should be propagationPolicy=Orphan. But it does not work. * Kubectl still use orphanDependents.: https://github.com/kubernetes/kubernetes/blob/master/pkg/kubectl/delete.go#L388 * kubernetes/kubernetes#46659
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Forked from #46471 (comment) based on discussion with @caesarxuchao.
kubectl, today, uses DeleteOptions.OrphanDependents field to do cascading deletion.
We need to do the following to update kubectl to use PropagationPolicy instead.
The text was updated successfully, but these errors were encountered: