This repository has been archived by the owner on Mar 4, 2024. It is now read-only.
EVEREST-406 Increased timeout for installing operators #152
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
gen1us2k
requested review from
recharte and
oksana-grishchenko
as code owners
Codecov Report
@@ Coverage Diff @@
## main #152 +/- ##
=====================================
Coverage 5.12% 5.12%
=====================================
Files 12 12
Lines 2788 2788
=====================================
Hits 143 143
Misses 2621 2621
Partials 24 24
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
oksana-grishchenko
approved these changes
Sep 25, 2023
ghost
approved these changes
Sep 26, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
5-minute timeout should be enough to create an install plan on slow Kubernetes clusters or on clusters with high latency. We had this timeout in PMM/DBaaS for a while and all operators were installed successfully. I tested it on clean GKE deployment using Danil's laptop and it ran successfully.
The original stacktrace shows that it failed because 2.5 minutes were not enough to create an install plan for the Postgres operator and it gets created a couple of moments later