Tenant admin view - #10
Conversation
…eource and logs admin resource on case the user field is enabled
…ne along wiht the user field name in cfg
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: bro-adm The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Hi @bro-adm. Thanks for your PR. I'm waiting for a ViaQ member to verify that this patch is reasonable to test. If it is, they should reply with Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
In rhoai we have a case of usage logs that include user_id structured metadata unindexed field.
that means the usual namepsace based access control via role bindings on the tenant and logs resource on namespaces is not enough as the only validation we would want.
We would have the rhoai admin that can access everything and that is handled via the OPA admin groups config.
The second layer would be a namespace logs admin that can query on all users on a namespace rather then just itself.