We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
"Terminal is disabled for cluster-admin users" is buried in the error message, and the prompt 'Please try again' stands out
Don't ask users to try again if they are doing something that isn't supported
Dont' present the web terminal icon in the console if I'm logged in as cluster admin
The context is that i'm tired and didn't notice the exact message, and I kept trying again (was just doing what the console said to do!)
The text was updated successfully, but these errors were encountered:
OpenShift 4.7 is going to have the ability for cluster-admins to user terminals. So, this issue is just waits until WTO 1.2 is realeased
Sorry, something went wrong.
thanks @sleshchenko will there be an option to disable cluster-admin access?
that was not planned and as result not implemented. What is the reason to disable it for cluster admin?
Just thought that some folks might want to enable web terminal for developers and not for cluster-admin, but that might just be my imagination ;)
No branches or pull requests
Is your enhancement related to a problem? Please describe.
"Terminal is disabled for cluster-admin users" is buried in the error message, and the prompt 'Please try again' stands out
Describe the solution you'd like
Don't ask users to try again if they are doing something that isn't supported
Describe alternatives you've considered
Dont' present the web terminal icon in the console if I'm logged in as cluster admin
Additional context
The context is that i'm tired and didn't notice the exact message, and I kept trying again (was just doing what the console said to do!)
The text was updated successfully, but these errors were encountered: