-
Notifications
You must be signed in to change notification settings - Fork 27
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
fix(rbac): sa and rbac definitions #117
fix(rbac): sa and rbac definitions #117
Conversation
Sync the SA and RBAC definitions with what we have in submariner-operator. Signed-off-by: Steve Mattar <smattar@redhat.com>
52366dc
to
ce9f395
Compare
verbs: | ||
- '*' | ||
- apiGroups: | ||
- lighthouse.submariner.io |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why does Engine Pod need access to lighthouse.submariner.io?
- pods | ||
- services | ||
- services/finalizers | ||
- endpoints | ||
- persistentvolumeclaims | ||
- events | ||
- configmaps | ||
- secrets | ||
verbs: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@SteveMattar Are we giving more permissions than what is really required?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sridhargaddam yes, I did not omit any role. The idea was to allow all permission the component used to have so that we don't break anything by mistake and the next step will be to remove uneeded roles.
This is what I have done in the operator as well.
Sync the SA and RBAC definitions with what we have in submariner-operator.
Signed-off-by: Steve Mattar smattar@redhat.com