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.

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

Enhance the output of PlacementDecision by including more details about the managed cluster #134

Closed
mikeshng opened this issue May 9, 2023 · 4 comments
Labels
enhancement New feature or request Stale

Comments

@mikeshng
Copy link
Member

mikeshng commented May 9, 2023

The PlacementDecision returns the set of managed cluster clusterNames.

status:
  decisions:
    - clusterName: cluster1
    - clusterName: cluster2
    - clusterName: cluster3

It maybe helpful to return other data as well such as the clusterClaims associated with the managed cluster along with the clusterName. This should be an opt-in only feature depending on the Placement spec.

Use case:

  1. The ArgoCD Cluster Decision Resource Generator uses duck-typing to specify the PlacementDecision in order to grab the set of OCM clusterNames for ApplicationSet template evaluation. In addition to clusterNames, it will be nice to have other details about the clusters as well so that more templating variables can be used.

  2. Allows human users and API consumers to generate a report on managed clusters easily.

@mikeshng mikeshng added the enhancement New feature or request label May 9, 2023
@mikeshng
Copy link
Member Author

mikeshng commented May 9, 2023

CC @haoqing0110 @qiujian16

@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
@qiujian16 qiujian16 removed the Stale label Jul 14, 2023
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
@haoqing0110 haoqing0110 reopened this Nov 27, 2023
@haoqing0110 haoqing0110 removed the Stale label Nov 27, 2023
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
zhujian7 pushed a commit to zhujian7/ocm that referenced this issue Nov 12, 2024
Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
Co-authored-by: red-hat-konflux[bot] <126015336+red-hat-konflux[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Stale
Projects
None yet
Development

No branches or pull requests

3 participants