update SpreadConstraint fields, use maxGroups and minGroups instead of maximum and minimum. #162
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
instead of maximum and minimum. Signed-off-by: Kevin Wang <kevinwzf0126@gmail.com>
jwcesign
pushed a commit
to jwcesign/karmada
that referenced
this pull request
Feb 22, 2023
Add docs `userguide`
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.
Signed-off-by: Kevin Wang kevinwzf0126@gmail.com
What type of PR is this?
/kind api-change
What this PR does / why we need it:
Improve API readability, use maxGroups and minGroups instead of maximum and minimum in spreadConstraint
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: