-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
Standard SA User doesn't have access to listen events on OCP4 #8
Comments
How does your CR look like? |
By default any Deployment get a SA in OCP4.
I changed the CR to use specific SA "default". Doesn't work either. The User needs more permission (RBAC).
|
The generated role is defined here: https://github.com/bakito/k8s-event-logger-operator/blob/master/pkg/controller/eventlogger/eventlogger_controller.go#L494 |
this is the API call from OC client |
Getting the latest revision was not limitted to the watch namespace. Hence a cluster role was required. |
Which RBAC should be added?
......
{"level":"error","ts":1575727481.5853245,"logger":"cmd","msg":"","error":"events is forbidden: User "system:serviceaccount:test-event-logger:event-logger-example-eventlogger" cannot list resource "events" in API group "" at the cluster scope","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-logr/zapr@v0.1.1/zapr.go:128\nmain.main\n\t/build/cmd/logger/main.go:114\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:203"}
The text was updated successfully, but these errors were encountered: