-
Notifications
You must be signed in to change notification settings - Fork 821
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
NoSchedule taint for Cluster object not works #4952
Comments
We can take a look together |
I understand that this should not be expected. |
I don't quite understand. Isn't this saying that the taint is tolerated? Scheduling it should be a normal situation, right? If we don't declare tolerance, everything will be scheduled to member2. |
Hi @dominicqi
No, the policy is: clusterTolerations:
- effect: NoSchedule
key: workload-rebalancer-test
operator: Exists
tolerationSeconds: 0 In here, Since cluster member1 has However, now, we still schedule replicas to member1 cluster, which means the taint is not work, and it is not expected. |
Hi @chaosi-zju
I understand what you are saying. One thing I am confused about is whether this has a special meaning in Karmada? The Kubernetes documentation has such a description
|
What happened:
I add a
NoSchedule
taint to member1 Cluster as:Then I create a new deployment and propagate it to member1 and member2 cluster by a dynamic weight Policy whose
clusterTolerations
is defined as:Since member1 cluster has
NoSchedule
taint, it should be all propagated to member2 cluster, but the actual result is both member1 and member2 cluster been propagated.What you expected to happen:
the replicas should be all propagated to member2 cluster.
How to reproduce it (as minimally and precisely as possible):
1)add
NoSchedule
taint to member1 cluster2)write following yaml to local file
resource.yaml
resource.yaml
3)check the schedule result in binding.
I0516 13:04:56.030578 1 event.go:376] "Event occurred" object="default/demo-deploy-1" fieldPath="" kind="Deployment" apiVersion="apps/v1" type="Normal" reason="ScheduleBindingSucceed" message="Binding has been scheduled successfully. Result: {member2:2, member1:1}"
Anything else we need to know?:
Environment:
kubectl-karmada version
orkarmadactl version
): latestThe text was updated successfully, but these errors were encountered: