What did you do to encounter the bug?
Kubernetes has some default user-facing roles (admin, edit, view) which can be auto-reconciled based on labels. User-Facing Roles
This way, new custom resources can be added to the standard permissions automatically.
This is particularly useful for cluster admins to give standardized roles to users (ex: Rancher project admin, member, reader permissions).
What did you expect?
When mongodb operator is installed:
Default admin role should have permission to all verbs the CR API Group: mongodbcommunity.mongodb.com
Default edit role should have permission to write verbs the CR API Group: mongodbcommunity.mongodb.com
Default view role should have permission to read verbs the CR API Group: mongodbcommunity.mongodb.com
Admin can/should be combination of edit and view roles instead of a separate role by itself.
See Fluxcd's example: Flux User Edit RoleWhat happened instead?
User facing roles are not auto-reconciled.
This issue is being marked stale because it has been open for 60 days with no activity. Please comment if this issue is still affecting you. If there is no change, this issue will be closed in 30 days.
What did you do to encounter the bug? Kubernetes has some default user-facing roles (admin, edit, view) which can be auto-reconciled based on labels. User-Facing Roles This way, new custom resources can be added to the standard permissions automatically. This is particularly useful for cluster admins to give standardized roles to users (ex: Rancher project admin, member, reader permissions).
What did you expect? When mongodb operator is installed:
mongodbcommunity.mongodb.com
mongodbcommunity.mongodb.com
mongodbcommunity.mongodb.com
Admin can/should be combination of edit and view roles instead of a separate role by itself. See Fluxcd's example: Flux User Edit Role What happened instead? User facing roles are not auto-reconciled.