We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
What happened:
spec: placement: clusterAffinity: clusterNames: - member1 replicaScheduling: replicaDivisionPreference: Weighted replicaSchedulingType: Divided weightPreference: dynamicWeight: AvailableReplicas
spec: placement: clusterAffinity: clusterNames: - member2 # this line changed replicaScheduling: replicaDivisionPreference: Weighted replicaSchedulingType: Divided weightPreference: dynamicWeight: AvailableReplicas
i hope the deployment can be moved to member2 cluster, but nothing happend. i think the problem may be here: https://github.com/karmada-io/karmada/blob/master/pkg/scheduler/core/division_algorithm.go#L36
Accoding to this logic, in the above case, assignedReplicas == spec.Replicas ==> the target clusters not changed ==> no need to reschedule
Environment:
kubectl-karmada version
karmadactl version
The text was updated successfully, but these errors were encountered:
I've just tested it
/assign
Sorry, something went wrong.
@Garrybest @huone1
it is resolved in PR #1383
Yeah I just took a look at #1383 and it should work
/assign @huone1
huone1
Successfully merging a pull request may close this issue.
What happened:
i hope the deployment can be moved to member2 cluster, but nothing happend.
i think the problem may be here: https://github.com/karmada-io/karmada/blob/master/pkg/scheduler/core/division_algorithm.go#L36
Accoding to this logic, in the above case, assignedReplicas == spec.Replicas ==> the target clusters not changed ==> no need to reschedule
Environment:
kubectl-karmada version
orkarmadactl version
):The text was updated successfully, but these errors were encountered: