Bug 1986033 - cluster_quantile:apiserver_request_duration_seconds:histogram_quantile recording rule shipped by both CMO and cluster-kube-apiserver-operator
Summary: cluster_quantile:apiserver_request_duration_seconds:histogram_quantile recor...
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 4.9
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.9.0
Assignee: Arunprasad Rajkumar
QA Contact: Junqi Zhao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-26 14:38 UTC by Simon Pasquier
Modified: 2021-09-20 13:33 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-08-16 07:03:57 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-monitoring-operator pull 1316 0 None None None 2021-08-10 11:52:01 UTC

Description Simon Pasquier 2021-07-26 14:38:06 UTC
Description of problem:
cluster_quantile:apiserver_request_duration_seconds:histogram_quantile is shipped both by CMO via the openshift-monitoring/kubernetes-monitoring-rules PrometheusRule resource and cluster-kube-apiserver-operator via the openshift-kube-apiserver/kube-apiserver-slos PrometheusRule resource.

Version-Release number of selected component (if applicable):
4.9

How reproducible:
Always

Steps to Reproduce:
Run the following command:

oc get prometheusrule -A -o json | jq '.items | map({name: .metadata.name, ns: .metadata.namespace, groups: .spec.groups})  | map( select( .groups | any(.rules | any(.record == "cluster_quantile:apiserver_request_duration_seconds:histogram_quantile")))) | map(.ns + "/" + .name)'  

Actual results:

[
  "openshift-kube-apiserver/kube-apiserver-slos",
  "openshift-monitoring/kubernetes-monitoring-rules"
]

Expected results:


[
  "openshift-kube-apiserver/kube-apiserver-slos"
]

Additional info:

AFAICT the issue is only present in 4.9 because the rules have been reorganized/split by https://github.com/kubernetes-monitoring/kubernetes-mixin/pull/632 which hasn't been pulled in 4.8.


Note You need to log in before you can comment on or make changes to this bug.