-
Notifications
You must be signed in to change notification settings - Fork 94
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
Comments
Message to comment on stale issues. If none provided, will not mark issues stale |
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 |
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 |
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>
The PlacementDecision returns the set of managed cluster clusterNames.
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:
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.
Allows human users and API consumers to generate a report on managed clusters easily.
The text was updated successfully, but these errors were encountered: