-
Notifications
You must be signed in to change notification settings - Fork 140
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
Allow access to DataScienceCluster component statuses for basic OpenShift Console users #588
Labels
enhancement
New feature or request
Comments
i think the more accurate one to use is |
This was referenced Oct 18, 2023
It should be noted -- this seems not possible to do at a subresource only level. My test & results can be found on slack. |
Migrated to JIRA: https://issues.redhat.com/browse/RHOAIENG-493, hence closing it here. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
The Dashboard would like to start relying heavily on the status of the Operator's DSC CR, so we can know what components are installed so we can override our feature flags. Ideally this will grow to support issues with installation issues of components. (eg. opendatahub-io/odh-dashboard#1886 -- which seems to have some details already)
Describe the solution you'd like
An out-of-the-box role to grant all
system:authenticated
users access to the.status
of the DSC.akin to
kubectl create role foo --verb=get,list,watch --resource=pods/status
Describe alternatives you've considered
Additional context
A final note on how we approach this: we will just have to be careful about any information we put on the status and make sure we aren’t leaking any potentially sensitive information about the underlying cluster. Such as any human readable messages
The text was updated successfully, but these errors were encountered: