This repository has been archived by the owner on Oct 24, 2023. It is now read-only.
test: wait longer when incrementing error count waiting for pod Ready #560
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 implement the following algorithm when assessing for pod readiness in our E2E tests:
(The above algorithm is only implemented if n is greater than 1. If n is 1 then we simply wait for a single Ready response in a given timeout interval.)
In order to eliminate false positive signals due to "normal" operational pod reconciliation, we should wait longer if we get a non-Ready signal, and allow the k8s control plane more time to reconcile the pod into a consistent Ready state.
Issue Fixed:
Requirements:
Notes: