-
Notifications
You must be signed in to change notification settings - Fork 953
Add flag for foregroundDeletion #672
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
Comments
possibly related: kubernetes/kubernetes#59850 |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
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 fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/reopen |
@avorima: You can't reopen an issue/PR unless you authored it or you are a collaborator. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@liztio I think this would be actually super useful, as the only way currently is through an unintuitive curl command. Can you reopen? |
There are three kinds of deletions apiserver supports: orphan, background, and foreground. Right now kubectl supports only orphan (--cascade=false) and background (--cascade=true). But there's no way to do a "foreground" deletion. In some cases foreground is required, for example when dependent resources need to be cleaned up for owner deletion to succeed.
I'd like to see
--propegation-policy=foreground
for this use case.The text was updated successfully, but these errors were encountered: