Increased wait time for initialize, runner and start jobs ready status. #161
Conversation
This file contains 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
|
|
|
Hi @prashanth-volvocars, sorry for such a delay! But I believe your use case should have been fixed during PR #169 so I close this PR - please use the v0.0.9rc3 or latest image. Feel free to re-open the PR it if needs be. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When K6-operator is installed in EKS Fargate, the test doesn't start as it takes longer than the default 60 seconds for the pods to become ready. Increased timeout will help operator to work normally in environments that take longer time for provisioning pods like EKS Fargate.