You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Kubernetes RBAC "Privilege Escalation Prevention" forbids rbac-manager from binding roles when rbac-manager itself does not have the permissions in said role.
This case is user error, but took several days to track down due to the lack of warning or error logs from rbac-manager
We encountered this when attempting to bind a create-namespace role, but had not granted that permission to rbac-manager.
My go fu is limited, but I think the Reconciler itself may have and return a useful errhere, but the wrapping code does nothing with it here. Though I'm surprised I was seeing no error output from this code...
The text was updated successfully, but these errors were encountered:
I think we should go ahead and move to the klog package and add logging levels with a lot more output at the higher levels. A general pass over the logging could be really good here.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
We've now run into two failure scenarios during
rbac-manager
's Reconciliation run where it failed to log anything relevant to:For example, the log output would end with
And no reference to error scenarios, for example:
rbac-manager
from binding roles whenrbac-manager
itself does not have the permissions in said role.rbac-manager
rbac-manager
fails because no namespaces exist which match a providednamespaceSelector.matchLabels
(see Rbac-manager doesn't handle the case where a namespace does not exist and is later created #53)My go fu is limited, but I think the
Reconciler
itself may have and return a usefulerr
here, but the wrapping code does nothing with it here. Though I'm surprised I was seeing no error output from this code...The text was updated successfully, but these errors were encountered: