operator-framework
Investigate listing cluster-catalog contents of very large catalogs with port-forwarding
For very large catalogs (such as registry.redhat.io/redhat/redhat-operator-index:v4.18 ; 1.55GB), listing the full contents of the catalog with port-forward may cause the request to time out before completion.
Investigate methods to list catalog contents for the purpose of listing available and installable package from the set of enabled catalogs.
One idea worth investigating would be to use the newly introduced /metas endpoint to get filtered (and cached) results we need rather then filtering full-catalog client-side, which should mitigate catalog-size issues.
It might potentially require extending /metas filtering capabilities to cover all use cases.
Issues go stale after 90 days of inactivity. If there is no further activity, the issue will be closed in another 30 days.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}