-
Notifications
You must be signed in to change notification settings - Fork 820
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
Karmada not propagate resources to new member cluster #2261
Comments
Yes, I think this is a reasonable use case. But now the scheduler doesn't re-schedule in case of cluster joining or removal. @dddddai I can see there is karmada/pkg/scheduler/scheduler.go Line 384 in ed9b838
|
Yeah I was thinking so, there were similar issues I think the descheduler should be responsible for this case? |
cc @Garrybest I'll pay attention to this feature. @dddddai can you help to lead the effort? |
Descheduler's duty is to evict replicas only. This issue focuses on scheduling a object to new joined clusters. I think we could always |
hello, is there anything new? |
@liuchintao we are working on it. @chaunceyjiang send a PR(#2301) for this. |
What happened:
I just want to propagate my deployment to all member clusters automatically, when they join.
After creating this PP, I find nginx deployment in cluster-1 and cluster-2.
But when I join a new member cluster-3, I find nginx deployment is not propagated to cluster-3
What you expected to happen:
Deployment should be propagated to new member cluster.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
kubectl-karmada version
orkarmadactl version
):The text was updated successfully, but these errors were encountered: