-
Notifications
You must be signed in to change notification settings - Fork 890
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Propose preferred cluster #3105
Propose preferred cluster #3105
Conversation
Any comments are welcome, just cc guys who might be interested in the feature. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some comments, there are more design points to discuss, thus I'd like to see a proposal been submitted
// Karmada scheduler could migrate workloads to the backup clusters. | ||
// | ||
// +optional | ||
OrderedClusterAffinity []OrderedClusterAffinity `json:"clusterPreferredAffinity,omitempty"` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OrderedClusterAffinity []OrderedClusterAffinity `json:"clusterPreferredAffinity,omitempty"` | |
OrderedClusterAffinity []OrderedClusterAffinityTerm `json:"clusterPreferredAffinity,omitempty"` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need to be plural? From the name, it's not clear that this is a slice.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice catch!
According to K8S API convention, Resource collections should be all lowercase and plural, whereas kinds are CamelCase and singular.
, at this point, we should use a plural
, it's the OrderedClusterAffinities
.
@kevin-wangzefeng What's your preference?
774edf6
to
666a43a
Compare
Signed-off-by: RainbowMango <qdurenhongcai@gmail.com>
666a43a
to
5c30415
Compare
Codecov Report
📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more @@ Coverage Diff @@
## master #3105 +/- ##
==========================================
- Coverage 48.50% 48.49% -0.02%
==========================================
Files 201 201
Lines 18127 18127
==========================================
- Hits 8793 8791 -2
- Misses 8848 8850 +2
Partials 486 486
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind api-change
/kind feature
What this PR does / why we need it:
This PR addresses the discussions on issues #780 and #2085 and part of the discussion on slack.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
This PR just focuses on API change on PropagationPolicy, the complete plan is still ongoing, the following main task would be:
Does this PR introduce a user-facing change?: