-
Notifications
You must be signed in to change notification settings - Fork 530
Conversation
634d607
to
3a6f119
Compare
/retest |
25bd481
to
a84e4a5
Compare
/retest |
/test |
@xunpan: No presubmit jobs available for kubernetes-sigs/kubefed@master In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@irfanurrehman |
Thanks for doing this @xunpan. I will positively take a look at this tomorrow. |
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.
@xunpan Many thanks for spending time on this.
However, I think there is some rework that would be needed on this PR. Please take a look at my comments.
pkg/apis/scheduling/v1alpha1/replicaschedulingpreference_types.go
Outdated
Show resolved
Hide resolved
pkg/apis/scheduling/v1alpha1/replicaschedulingpreference_types.go
Outdated
Show resolved
Hide resolved
pkg/schedulingtypes/plugin.go
Outdated
if p.typeConfig.GetNamespaced() { | ||
return util.ComputeNamespacedPlacement(fedObject, fedNsObject, clusters, p.limitedScope) | ||
} | ||
return util.ComputePlacement(fedObject, clusters) |
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.
Please see my comment above about using this as is here. I think we need a separate function which gets only the clusterselector from the target resource. We are trying to intersect with the clusterselector only, not the clusternames.
return ctlutil.StatusError | ||
} | ||
|
||
preferredClusters := []string{} |
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.
Could not understand the need of preferredClusters
it seems to be a copy of resultClusters
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.
nit: @xunpan this is still unresolved but I will approve as this does not seem to harm the logic at all.
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.
Could you add some documentation with an example as part of our current docs ?
@xunpan Could you address the requested changes by @irfanurrehman ? |
Yes. The code was done and I'm testing it locally. The updated diff will be committed by this week. |
@xunpan I missed checking on this. I see that you did some updates. Were they finalised by you? Should I check them again? |
@irfanurrehman I forgot to send you a message after update the PR. I think I addressed your comments above. One does not changed: |
Thanks for doing this @xunpan. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: irfanurrehman, xunpan 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 this PR does / why we need it:
We add intersection behavior because it makes sense to result placement for resource propagation.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #981
Special notes for your reviewer:
RSP
for placement calculation