This repository has been archived by the owner on Oct 18, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 30
Will Placement support replicas scheduling? #96
Comments
This is a good idea, it is needed in actual use |
What's the expected input and output? Currently, the placementdecision only contains a list of cluster names. |
@haoqing0110 would you help to move this issue to ocm repo. I am going to archive this repo. |
@qiujian16 yes, copied to open-cluster-management-io/ocm#655 . |
/close |
@haoqing0110: Closing this issue. 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-sigs/prow repository. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
for example, global replicas is 10, and 2 in cluster1, 3 in cluster2, 5 in cluster3 after scheduling.
The text was updated successfully, but these errors were encountered: