+++ This bug was initially created as a clone of Bug #1955445 +++ Description of problem: The CRI-O service exposes metrics about container images which can have very high cardinality for clusters running many different images (e.g. CI clusters). These metrics aren't used actually anywhere (neither rules nor dashboards) and storing them in Prometheus increases memory usage by a lot (on some clusters, they account for more than 50% of the total series). Version-Release number of selected component (if applicable): 4.6 How reproducible: Always Steps to Reproduce: 1. Open the Prometheus UI, go to the Status > TSDB status page and look at the "Top 10 series count by metric names" section. Actual results: The following metrics (at least part of them) are listed: - container_runtime_crio_image_pulls_by_digest - container_runtime_crio_image_layer_reuse - container_runtime_crio_image_pulls_by_name - container_runtime_crio_image_pulls_successes Expected results: These metrics aren't present. Additional info: The following query returns the number of series per CRI-O metric: sort_desc(count by(__name__) ({job="crio"})) It can be used to verify that the container_runtime_crio_image_* metrics aren't present anymore.
tested with the PR not merged, no container_runtime_crio_image_* metrics now # 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/label/__name__/values' | jq | grep container_runtime_crio_image no result
based on Comment 3, move to VERIFIED, there are acceptable payloads which include the fix
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 (Moderate: OpenShift Container Platform 4.7.12 bug fix and security update), 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/RHSA-2021:1561