fix(k8s): wait for pool ready when upgrading cluster #2427
Merged
Conversation
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
Mia-Cross
force-pushed
the
k8s_pool_wait_upgrade
branch
from
5ebb4d3 to
26625c3
Compare
Mia-Cross
force-pushed
the
k8s_pool_wait_upgrade
branch
from
e803000 to
8dfc965
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2427 +/- ##
==========================================
- Coverage 73.74% 73.74% -0.01%
==========================================
Files 229 229
Lines 35761 35768 +7
==========================================
+ Hits 26371 26376 +5
- Misses 7115 7116 +1
- Partials 2275 2276 +1 ☔ View full report in Codecov by Sentry. |
remyleone
reviewed
Feb 29, 2024
remyleone
approved these changes
Feb 29, 2024
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.
Closes #2407
(This PR is a duplicate of #2416 that I closed before doing the update of the sdk and couldn't open again because of a force-push)