[feature]Replace update #147
Merged
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
|
CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅ |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #147 +/- ##
==========================================
+ Coverage 63.83% 63.99% +0.16%
==========================================
Files 72 72
Lines 4731 4736 +5
==========================================
+ Hits 3020 3031 +11
+ Misses 1426 1422 -4
+ Partials 285 283 -2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
|
I have read the CLA Document and I hereby sign the CLA |
dbug-dk
force-pushed
the
replaceUpdate
branch
3 times, most recently
from
02f9d00
to
83ddd82
Compare
dbug-dk
force-pushed
the
replaceUpdate
branch
from
d77f77d
to
56fd06e
Compare
wu8685
reviewed
Jan 12, 2024
1. use replace new id instead of new pod name 2. allocate id when replaceUpdate needed. 3. judge whether pod need update based on whether it is in the "replace" state.
wu8685
reviewed
Feb 18, 2024
…he process of creating pod and delete pod in replace update and specify pod replace
wu8685
reviewed
Mar 6, 2024
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.
1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):
#111
2. What is the scope of this PR (e.g. component or file name):
3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):
4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):
5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:
6. Release note
Please refer to Release Notes Language Style Guide to write a quality release note.