Increase kubectl wait timeout for scale-from-zero alpine pods#13655
Merged
Increase kubectl wait timeout for scale-from-zero alpine pods#13655
Conversation
Signed-off-by: Botond Szirtes <botond.szirtes@est.tech>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The
alpinepod in scale-from-zero tests requires the NSE to be spawned on-demand before it can become ready. On loaded CI runners this chain (NSC triggers supplier → NSE spawned → NSE registers → NSC connects) consistently exceeds the previous 1m timeout, causing failures across all kind versions.Increase the timeout to 2m for both
scale-from-zeroandvl3-scale-from-zeroto give enough headroom on constrained runners.