feat: add topologyspreadconstraints for service#100
Merged
liu-hm19 merged 6 commits intoKusionStack:mainfrom Nov 21, 2024
Merged
feat: add topologyspreadconstraints for service#100liu-hm19 merged 6 commits intoKusionStack:mainfrom
liu-hm19 merged 6 commits intoKusionStack:mainfrom
Conversation
Yangyang96
reviewed
Nov 21, 2024
Yangyang96
reviewed
Nov 21, 2024
Yangyang96
reviewed
Nov 21, 2024
|
The comments are clear and straightforward, and the code is properly formatted! Thank you for your contribution! @gshilei |
gshilei
force-pushed
the
add-topologyspreadconstraints
branch
from
4723437 to
b205227
Compare
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
3 participants
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.
What type of PR is this?
What this PR does / why we need it:
PR for issue KusionStack/kusion#1303
Please help to have a review. Thanks.
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., design docs, usage docs, etc.: