prometheus-adapter is currently only being monitored via means of availability in the api service Kubernetes registry. We miss a proper service monitor. Additionally we could gain insights in the future. It was contributed upstream https://github.com/coreos/kube-prometheus/pull/622 and we should enable it downstream too.
This was just posted, there was no time to add support this sprint.
setting priority to high but severity to low. reasoning: we really want this in, preferably in 4.6. But if 4.6 ships without it nothing breaks.
UpcomingSprint: not enough time/capacity to tackle the issue this sprint.
tested with 4.6.0-0.nightly-2020-09-12-230035, prometheus-adapter servicemonitor is added, and the targets are monitored # oc -n openshift-monitoring get servicemonitor prometheus-adapter NAME AGE prometheus-adapter 4h12m # oc -n openshift-monitoring get ep prometheus-adapter NAME ENDPOINTS AGE prometheus-adapter 10.128.2.6:6443,10.131.0.5:6443 4h19m # token=`oc sa get-token prometheus-k8s -n openshift-monitoring` # oc -n openshift-monitoring exec -c prometheus prometheus-k8s-0 -- curl -k -H "Authorization: Bearer $token" 'https://prometheus-k8s.openshift-monitoring.svc:9091/api/v1/targets' | jq | grep -E "\"scrapePool\"|\"scrapeUrl\"|\"health\"" | grep "prometheus-adapter" -A3 "scrapePool": "openshift-monitoring/prometheus-adapter/0", "scrapeUrl": "https://10.128.2.6:6443/metrics", "health": "up" "scrapePool": "openshift-monitoring/prometheus-adapter/0", "scrapeUrl": "https://10.131.0.5:6443/metrics", "health": "up"
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 (OpenShift Container Platform 4.6 GA Images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4196