You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
synchronously looping over thos namespaces listing all resources in each namespace
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:
Collect a list of all namespaces where the user has any permissions
Using the admin client do a cluster-wide list with label selectors that filter by .metadata.namespace being in the set of authorized namespaces
TODO
Add smoke tests for listing all resources with and without permissions
Write a ginkgo Measure test for listing apps and run with 1, 10, 100 and 1000 orgs/spaces containing one app
The text was updated successfully, but these errors were encountered:
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 <[email protected]>
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 <[email protected]>
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: