[RBAC] Unable to edit/add monitoring to a already created DB cluster, with specific RBAC policy
Description
STRs: 1. Install Everest v1.4 rc-5 2. Create a DB cluster without monitoring enabled in a namespace. 3. Add two monitoring endpoints for that namespace. 2. Apply the following RBAC policy for monitoring: p, role:test, monitoring-instances, *, */<one of the monitoring endpoint> OR p, role:test, monitoring-instances, *, <namespace>/<one of the monitoring endpoint> 3. Open the DB cluster overview
Actual Outcome: Monitoring edit option not visible on the UI for any db cluster in the namespace.
Expected Outcome: Monitoring option visible on the UI for db clusters in the namespace.
Video attached in the comment section of
Environment
None
Attachments
1
Activity
Yusaf Awan
January 30, 2025 at 1:31 PM
Tested and verified:
Fábio Da Silva
January 23, 2025 at 11:12 PM
General FB w/RBAC fixes:
Diogo Recharte
January 21, 2025 at 11:34 AM
Waiting for the remaining tickets of everest-1.5.0-rbac-fixes to be ready, then a FB will be created with all of them.
High
STRs:
1. Install Everest v1.4 rc-5
2. Create a DB cluster without monitoring enabled in a namespace.
3. Add two monitoring endpoints for that namespace.
2. Apply the following RBAC policy for monitoring:
p, role:test, monitoring-instances, *, */<one of the monitoring endpoint>
OR
p, role:test, monitoring-instances, *, <namespace>/<one of the monitoring endpoint>
3. Open the DB cluster overview
Actual Outcome:
Monitoring edit option not visible on the UI for any db cluster in the namespace.
Expected Outcome:
Monitoring option visible on the UI for db clusters in the namespace.
Video attached in the comment section of