e2e test to ensure graceful shutdown does not lose requests #3548
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.
What this PR does / why we need it:
It tests the bugfix which was introduced in #3536.
The bug stayed unnoticed for quite some time since it only breaks for slow requests if the timing is right. Related issue: #3533
Special notes for your reviewer:
I'm aware the test is potentially racy, since I don't ensure the HTTP request was made before starting pod shutdown and likewise don't keep the request going until the pod is in terminating phase. Running the e2e test locally and on Travis makes it spot the bug, though, if I revert #3536 (working vs broken).