Not all namespaces and helm charts show up

[rashid4lyf]

Description

We have deployed this onto a large cluster with over 300 helm charts however only 256 helm charts appear. We can see that in the request to get all namespaces, all namespaces are returned from the cluster (355 namespaces). However, some of these are not displayed as there are apparently no helm charts found which does not seem to be the case.

Is there a limit on the number of helm charts it can show or some known issue?

Screenshots

No response

Additional information

No response

[harshit-mehtaa]

Adding pagination might help here as in an instance only a specific set will be queried and loaded

[undera]

The 256 releases is a Helm default limit that we'll need to address either with higher limit or with pagination. It needs a fix in the code.

Infinite number of releases might be a wrong strategy, we should detect when we are hitting some limit and offer to narrow display down with namespace filter. TBD

The place where it originates from: https://github.com/helm/helm/blob/main/cmd/helm/list.go#L55

[rashid4lyf]

Thank you so much for the quick response! I think pagination would work well from a user experience point of view. Also, I assume one way to get around the limit is to show all namespaces and when you click on a namespace it would then find the charts for the given namespace?

[harshit-mehtaa]

@undera
Should we add pagination to1.x release? It would be easier to handle it using React on the frontend side
WDYT?

[undera]

I'm still in doubts. IMO pagination is wrong, 'cause you usually have idea about what you are looking for. It's either string pattern, or a namespace.
We can detect when there is more charts than we display, and suggest narrowing down the search. In this way, we'll have also to make filtering on backend, as opposed to current frontend way.
It definitely would need to wait for React