fix(frontend): restrict pods API based on namespace access
Description of your changes:
Closes #12509
View the linked issue for additional context and reproduction of the issue.
Test Evidence
User has access to activity in the namespace "serving-test-mlzone" but lacks access to "serving-test-s3":
User is blocked from displaying pod spec, logs, and events from a namespace they don't have access to through the backdoor URL manipulation:
UI functionality remains the same for users who do have access:
Checklist:
- [x] You have signed off your commits
- [x] The title for your pull request (PR) should follow our title convention. Learn more about the pull request title convention used in this repository.
Hi @demarna1. Thanks for your PR.
I'm waiting for a kubeflow member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.
Instructions 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/test-infra repository.
/ok-to-test
This is fantastic, @demarna1. Thank you for the contribution.
/lgtm /approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: droctothorpe, zazulam
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~frontend/OWNERS~~ [droctothorpe,zazulam]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
New changes are detected. LGTM label has been removed.