Skip to content
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

Feature: Add configuration to limits reading events to a specific namespace #52

Open
mavanier opened this issue Apr 21, 2021 · 0 comments
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. priority/P1 Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@mavanier
Copy link

/kind feature

What happened: Unable to specified a specific namespace to read events from

What you expected to happen:
In our cluster, we do not have the rights to see all cluster resources. By starting the application, we get the following exception.

E0421 17:03:18.033794       1 reflector.go:153] k8s.io/client-go/informers/factory.go:135: Failed to list *v1.Event: events is forbidden: User "system:serviceaccount:dev:event-exporter" cannot list resource "events" in API group "" at the cluster scope

How to reproduce it (as minimally and precisely as possible):

  • Create a new namespace
  • Create a new ServiceAccount in that namespace
  • Create a new RoleBinding to view clusterRole.
  • Bind the pod to the namespaced service account
  • Should see errors

Anything else we need to know?:
I tried installing it on OpenShift in a newly created namespace/project.

@caicloud-bot caicloud-bot added the kind/feature Categorizes issue or PR as related to a new feature. label Apr 21, 2021
@lichuan0620 lichuan0620 added help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. priority/P1 Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Apr 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. priority/P1 Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Development

No branches or pull requests

3 participants