This repository has been archived by the owner on Oct 24, 2023. It is now read-only.
test: increase e2e pod delete timeout tolerance to 5 mins #662
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reason for Change:
We regularly see pod deletes succeeding just above the current timeout threshold of 1 minute. E.g.:
There is no strict reason to enforce a 1 minute timeout generally for all pod delete operations. Let's increase to 5 mins to account for normal operational variance.
Issue Fixed:
Requirements:
Notes: