Description of problem:
Currently the new monitoring dashboards page is bypassing the recently created endpoint.
Based on the discussion with Andy, I'm assigning the issue to him, since he already has a good idea of what needs to be done.
Setting the target to 4.5 as this should not block release. Its a bug/tech debt.
(In reply to bpeterse from comment #2)
> Setting the target to 4.5 as this should not block release. Its a bug/tech
This one is probably a blocker because it means some users can't get the config maps. Moving back to 4.4.
We should also update to use the display names for the dashboards when we make this change.
I see it's targeted to 4.5.0, is this intended? comment 3 says that we need to fix in 4.4
Bug 1804918 is tracking the 4.4 fix.
1. Create metrics-reader cluster role and add user 'yapei' as metrics-reader
$ cat cluster-role.yaml
$ oc create -f cluster-role.yaml
$ oc adm policy add-cluster-role-to-user metrics-reader yapei1
2. user 'yapei1' login as a normal user and visit /monitoring/dashboards/ directly, user 'yapei1' can view all dashboards correctly in Monitoring -> Dashboards withour errors
# oc get cm -n openshift-config-managed
Error from server (Forbidden): configmaps is forbidden: User "yapei1" cannot list resource "configmaps" in API group "" in the namespace "openshift-config-managed"
Verified on 4.5.0-0.ci-2020-03-04-223611
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.