Skip to content

catalogd web api performance improvements RFC #1569

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.

Sign up for GitHub

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

Jump to bottom
Closed
Tracked by #1570
grokspawn opened this issue Nov 4, 2024 · 0 comments
Closed
Tracked by #1570

catalogd web api performance improvements RFC #1569

grokspawn opened this issue Nov 4, 2024 · 0 comments
Labels
v1.x Issues related to OLMv1 features that come after 1.0

Comments

@grokspawn
Copy link
Contributor

grokspawn commented Nov 4, 2024 •
edited
Loading

document for review: https://docs.google.com/document/d/1s6_9IFEKGQLNh3ueH7SF4Yrx4PW9NSiNFqFIJx0pU-8/
@grokspawn grokspawn mentioned this issue Nov 4, 2024
Open
12 tasks
@grokspawn grokspawn changed the title catalogd web api phase 2 RFC catalogd web api performance improvements RFC Dec 4, 2024
@grokspawn grokspawn added the v1.x Issues related to OLMv1 features that come after 1.0 label Dec 12, 2024
@camilamacedo86 camilamacedo86 transferred this issue from operator-framework/catalogd Jan 10, 2025
@grokspawn grokspawn moved this from Ready for Review to Accepted in OLM v1 Jan 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
v1.x Issues related to OLMv1 features that come after 1.0
Projects
OLM v1
Status: Accepted
Milestone
No milestone
Development

No branches or pull requests
1 participant
@grokspawn