-
Notifications
You must be signed in to change notification settings - Fork 3
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
User sees shared pipelines in Private section in Central Dashboard while not being a contributor in any namespace #56
Comments
/transfer dashboard |
@furiousassault: The label(s) In response to this:
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. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
/lifecyle frozen |
/kind bug
What steps did you take and what happened:
[A clear and concise description of what the bug is.]
We have a Kubeflow setup and switched REGISTRATION_FLOW variable to false to disable welcome screen and test manual namespace management.
When user is owning some empty namespace, or added as a contributor to such namespace, it sees no Private pipelines, as expected. But when we remove this user from contributors, so they doesn't have any namespaces, user sees all pipelines from Shared in Private section. User can successfully remove any of these "pipelines".
What did you expect to happen:
It is expected that he doesn't have access to the Dashboard at all, seeing some stub instead.
Or, if the "access without namespace" is valid scenario for work with shared entities, they are not shown in Private (namespaced) section.
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Operations on some other entities might also be affected.
Environment:
The text was updated successfully, but these errors were encountered: