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

Investigate listing cluster-catalog contents of very large catalogs with port-forwarding #1853

Open
ankitathomas opened this issue Mar 6, 2025 · 2 comments
Labels
epic/kubectl-operator-plugin v1.x Issues related to OLMv1 features that come after 1.0

Comments

@ankitathomas
Copy link
Contributor

ankitathomas commented Mar 6, 2025

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.

@azych
Copy link
Contributor

azych commented 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
Copy link
Contributor

azych commented Mar 17, 2025

/unassign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic/kubectl-operator-plugin v1.x Issues related to OLMv1 features that come after 1.0
Projects
Status: No status
Development

No branches or pull requests

2 participants