-
Notifications
You must be signed in to change notification settings - Fork 263
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
Add --wait
and --no-wait
for all delete operation
#671
Comments
/assign dsimansk |
See knative/serving#6876 for some example where this option is useful. I think also that |
PR #682 extends current wait functionality to allow waiting for various events. To complete this issue synchronous
|
/reopen To do: sync revision delete. |
@dsimansk: Reopened 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. |
* retry different regions/zones * update with PR comments * Update scripts/README.md Co-Authored-By: chaodaiG <[email protected]> * update based on PR feedback * Update scripts/e2e-tests.sh Co-Authored-By: chaodaiG <[email protected]> * update based on PR feedback
* Poke CI * 0.17.2 svc.ci -> ci
In what area(s)?
Describe the feature:
In order to avoid race conditions when on delete an object and immediately recreate it, by default we should also wait for the end of a delete operation, like we do for
service create
andservice update
.Therefor a
--wait
and a--no-wait
option should be added to all "delete" operation. This can reuse our general wait handling util libs.The text was updated successfully, but these errors were encountered: