The UI currently uses multiple sources to render Fleet information, including GitRepos and BundleDeployments. In particular, computing the list of resources for a GitRepo is very resource-intensive, sometimes causing the UI to temporarily freeze.
Initial investigation shows that starting on Fleet 0.10, the gitrepo.status.resources field now contains one entry per resource and cluster, while the UI would still consider it unique and try to correlate that with the BundleDeployments hence calculating (and effectively duplicating) the resource list.
aruiz14
commented
1 day ago
The UI currently uses multiple sources to render Fleet information, including GitRepos and BundleDeployments. In particular, computing the list of resources for a GitRepo is very resource-intensive, sometimes causing the UI to temporarily freeze. Initial investigation shows that starting on Fleet 0.10, the
gitrepo.status.resourcesfield now contains one entry per resource and cluster, while the UI would still consider it unique and try to correlate that with the BundleDeployments hence calculating (and effectively duplicating) the resource list.Related: