-
Notifications
You must be signed in to change notification settings - Fork 40
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: restrict permissions to only access specific CRB #436
Conversation
e1b9184
to
7fa9471
Compare
Codecov Report
@@ Coverage Diff @@
## main #436 +/- ##
=======================================
Coverage 78.00% 78.00%
=======================================
Files 21 21
Lines 1323 1323
=======================================
Hits 1032 1032
Misses 251 251
Partials 40 40
Flags with carried forward coverage won't be shown. Click here to find out more. |
Signed-off-by: Florian Bacher <[email protected]>
Signed-off-by: Florian Bacher <[email protected]>
33c8260
to
203f638
Compare
Signed-off-by: Florian Bacher <[email protected]>
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.
LGTM but I would double check with the helm package step if we lock down the name there as well
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.
Reviewing the BackfillPermissions
method, this looks right to me. I dont think we need anything else.
Once #377 has been implemented, this permission can likely be dropped completely
@bacherfl I think the above issue is basically done by @james-milligan with #412, but I think the plan was not to get rid of the direct k8s sync at least for now. So I think we will need to keep this until we decide to move away from that (if we do at all).
This PR reduces the required permissions for the OFO to only be able to modify the
open-feature-operator-flagd-kubernetes-sync
ClusterRoleBinding.Once #377 has been implemented, this permission can likely be dropped completely