-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Disable auth error notifications #4941
Comments
There is no way to disable them, unfortunately. We need to improve this behavior and allow only unique errors to appear and not stack them indefinitely. This should partially solve the issue. We might also add some switch on the settings page to filter out auth errors from the notifications panel. |
Thanks! I'll keep an eye on it for the future. |
I'll actually keep that open as a feature request. /reopen |
@floreks: Reopened this issue. 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 is for the dashboard v2.0.0-beta6.
Hi All,
I have configured a dashboard token identify that has read-only access to everything in the k8s installation except the secrets in each namespace. When viewing the dashboard, the "notifications center" on the top right continuously fills up with errors of the like:
"system:serviceaccount:kubernetes-dashboard:kubernetes-dashboard"
cannot list resource "secrets" in API group "" in the namespace "foo"
This is "correct" in that we don't want access to secrets, but the dashboard seems very aggressive in trying to access those secrets, and it results in a very large number of errors. At the rate of about 1 error per 10 seconds or so. I don't see it in the documentation, but is there a way to either disable those error messages in the notification center, disable the notification center altogether or somehow otherwise stop the flow of errors?
Thanks for all the good work!
The text was updated successfully, but these errors were encountered: