Investigate listing cluster-catalog contents of very large catalogs with port-forwarding #1853
Description
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.
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
Milestone
Relationships
Development
No branches or pull requests
Participants
Activity
kubectl operatorplugin updates for operator-controller and catalogd #1424azych commentedon Mar 17, 2025
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.
azych commentedon Mar 17, 2025
/unassign
github-actions commentedon Jun 25, 2025
Issues go stale after 90 days of inactivity. If there is no further activity, the issue will be closed in another 30 days.
ankitathomas commentedon Nov 3, 2025
See https://hackmd.io/uupzJCqGTny24Ngjvb9JaA