-
Notifications
You must be signed in to change notification settings - Fork 71
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
Improve listing resources in authorized namespaces #3636
Labels
Comments
danail-branekov
added a commit
that referenced
this issue
Jan 7, 2025
The tests verify that * Authorised users can list resources * Unauthorised users get empty resources list but no error issue #3636 Co-authored-by: Georgi Sabev <georgethebeatle@gmail.com>
georgethebeatle
added a commit
that referenced
this issue
Jan 7, 2025
The tests verify that * Authorised users can list resources * Unauthorised users get empty resources list but no error issue #3636 Co-authored-by: Georgi Sabev <georgethebeatle@gmail.com>
Here are some performance results with The test creates one-app-spaces in a single org and scales this setup. v0.13.0
main
|
github-project-automation
bot
moved this from 🔄 In progress
to ✅ Done
in Korifi - Backlog
Jan 13, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Background
When listing resources we have established the pattern of
The goal of this pattern is to prevent the listing of resources that the user may not have permissions to see
The problem with this approach is performance - it is suboptimal to do so many requests and the overall time of listing grows linearly with the number of spaces.
Proposal
Use the admin client to do a cluster-wide list as follows:
.metadata.namespace
being in the set of authorized namespacesTODO
Measure
test for listing apps and run with 1, 10, 100 and 1000 orgs/spaces containing one appThe text was updated successfully, but these errors were encountered: