-
Task
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
Product / Portfolio Work
-
False
-
-
False
-
5
-
None
-
None
-
Sprint 271, Sprint 272, Sprint 273
Tests
- Test for regressions regarding the Perses dashboards for the monitoring plugin
- After upgrading, access to dashboards might be disallowed as there was no RBAC
- RBAC:
- UI Tech sync May 8th - Testing section
-
-
- Create a dev user 1
- Add a role bindings to dev user 1 for a specific dashboard and data source in a namespace
- Check that dev user 1 can see data
- Create a dev user 2
- Check that dev user 2 cannot see dev user 1 dashboard
Resources to be handled:
-
-
-
- Namespace, Dashboard, Datasource permissions
- ClusterRoles, RoleBindings
- Usernames with different special chars. Good to check what kind of login providers, integrations OCP has and their rules for usernames to mimic
-
- clones
-
-
- Closed
-
- depends on
-
OU-697 Evaluate Perses RBAC integration with k8s
-
- Closed
-
- is related to
-
COO-1038 Perses operator and monitoring perses dashboard
-
- Closed
-
-
OU-861 [Perses RBAC][to be evaluated] - When creating a ClusterRoleBinding for user1 as roleRef persesdashboard-editor-role, even if you delete it you still have access to it
-
- Closed
-
-
-
- Closed
-