-
Epic
-
Resolution: Done
-
Normal
-
None
-
None
-
alertmanager view role
-
False
-
None
-
False
-
Not Selected
-
NEW
-
To Do
-
NEW
-
0% To Do, 0% In Progress, 100% Done
-
Allow read-only access (get and list only) to the Alertmanager API through the monitoring-alertmanager-view role.
-
Enhancement
$ oc get clusterrole,role -n openshift-monitoring -o name | egrep -i -e 'monitoring{-}(alertmanager|rules)-(edit|view)' -e cluster-monitoring-view clusterrole.rbac.authorization.k8s.io/cluster-monitoring-view clusterrole.rbac.authorization.k8s.io/monitoring-rules-edit clusterrole.rbac.authorization.k8s.io/monitoring-rules-view clusterrole.rbac.authorization.k8s.io/openshift-cluster-monitoring-view role.rbac.authorization.k8s.io/monitoring-alertmanager-edit
we have cluster roles for viewing metrics and editing alerts/silences but not a local role for viewing all.
I have a customer requesting read only access to alerts in the developer console.
- is blocked by
-
MON-3381 Replace oauth-proxy container with kube-rbac-proxy in Alertmanager pods
-
- Closed
-
- is documented by
-
OBSDOCS-1110 Document new monitoring-alertmanager-view role for Alertmanager API
-
- Closed
-
- is related to
-
OTA-1080 Proof-of-concept oc access to firing alerts
-
- Closed
-
- relates to
-
OCPBUGS-17850 common user can view UWM alertmanager alerts
-
- Closed
-
1.
|
Post-merge Testing |
|
Closed | 
|
Junqi Zhao |
2.
|
E2E Automation |
|
Closed |
|
Junqi Zhao |
3.
|
CI Integration |
|
Closed |
|
Junqi Zhao |
