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

Feature Request: extend GitRepoStatus for easier differentiation of per-cluster state #3186

Open
aruiz14 opened this issue Jan 8, 2025 · 1 comment

Comments

@aruiz14
Copy link
Contributor

aruiz14 commented Jan 8, 2025

Is your feature request related to a problem?

While working on #3102 and rancher/dashboard#12424, I realized that the dashboard has to do non-trivial computations in order to differentiate each cluster, which actually lead to a bug that made the resource list not to contain accurate information.

Solution you'd like

The UI was changed to use BundleDeployments for calculating the list of resources, but Fleet could ease this task by exposing the necessary information in a way that can directly be consumed (as far as I could see, Fleet is already doing the computation part that would allow this, it only needs to extend its API to expose it).

Alternatives you've considered

No response

Anything else?

No response

@aruiz14 aruiz14 self-assigned this Jan 8, 2025
@aruiz14 aruiz14 added this to the v2.11.0 milestone Jan 8, 2025
@rancherbot rancherbot added this to Fleet Jan 8, 2025
@github-project-automation github-project-automation bot moved this to 🆕 New in Fleet Jan 8, 2025
@aruiz14 aruiz14 moved this from 🆕 New to 📋 Backlog in Fleet Jan 8, 2025
@manno
Copy link
Member

manno commented Jan 8, 2025

Referring this comment which has some example json: rancher/dashboard#11643 (comment)

The gitrepo.status.resources struct is not handling perCluster well. E.g. it has duplications. UI currently uses bd list instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 📋 Backlog
Development

No branches or pull requests

3 participants