Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Enhance the placement schedule time when add a new cluster #135

Closed
ldpliu opened this issue May 11, 2023 · 4 comments
Closed

Enhance the placement schedule time when add a new cluster #135

ldpliu opened this issue May 11, 2023 · 4 comments
Labels
enhancement New feature or request Stale

Comments

@ldpliu
Copy link
Contributor

ldpliu commented May 11, 2023

The placement schedule time is too long when add a new cluster.
steps:

  1. create 100 managedclusters
  2. create 100 placements which select these managedclusters
  3. create a new managedcluster which should also be selected by all the placements
  4. watch the placement schedule time(placement.Status.NumberOfSelectedClusters PlacementDecisions.Status.Decisions)

image

image
@ldpliu ldpliu added the enhancement New feature or request label May 11, 2023
@ldpliu ldpliu changed the title Enhance the placement schedule time when add a new cluster [Enhancement] Enhance the placement schedule time when add a new cluster May 11, 2023
@ldpliu ldpliu changed the title [Enhancement] Enhance the placement schedule time when add a new cluster Enhance the placement schedule time when add a new cluster May 11, 2023
@github-actions
Copy link

Message to comment on stale issues. If none provided, will not mark issues stale

@github-actions github-actions bot added the Stale label Jul 14, 2023
@zhujian7
Copy link
Member

/remove-stale

@qiujian16 qiujian16 removed the Stale label Jul 14, 2023
@xuezhaojun xuezhaojun moved this to To do in OCM releases Jul 17, 2023
@github-actions GitHub Actions
Copy link

This issue is stale because it has been open for 120 days with no activity. After 14 days of inactivity, it will be closed. Remove the stable label to prevent this issue from being closed.

@github-actions github-actions bot added the Stale label Nov 12, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 26, 2023
@github-project-automation github-project-automation bot moved this from To do to Done in OCM releases Nov 26, 2023
@haoqing0110 haoqing0110 reopened this Nov 27, 2023
@haoqing0110 haoqing0110 removed the Stale label Nov 27, 2023
@qiujian16 qiujian16 moved this from Done to To do in OCM releases Mar 6, 2024
@github-actions GitHub Actions
Copy link

This issue is stale because it has been open for 120 days with no activity. After 14 days of inactivity, it will be closed. Remove the stable label to prevent this issue from being closed.

@github-actions github-actions bot added the Stale label Mar 26, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 9, 2024
@github-project-automation github-project-automation bot moved this from To do to Done in OCM releases Apr 9, 2024
zhujian7 added a commit to zhujian7/ocm that referenced this issue Nov 28, 2024
@zhujian7
🌱 konflux: migration from 0.1 to 0.2 (open-cluster-management-io#135)
e74d5b5 
* yq format tekton files

Signed-off-by: zhujian <jiazhu@redhat.com>

* konflux: migration from 0.1 to 0.2

Signed-off-by: zhujian <jiazhu@redhat.com>

* upgrade konflux dockerfiles

Signed-off-by: zhujian <jiazhu@redhat.com>

---------

Signed-off-by: zhujian <jiazhu@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request Stale
Projects
OCM releases
Status: Done
Milestone
No milestone
Development

No branches or pull requests
4 participants
@qiujian16 @haoqing0110 @zhujian7 @ldpliu