This is a clone of issue OCPBUGS-34784. The following is the description of the original issue:
—
INSIGHTOCP-1557 is a rule to check for any custom Prometheus instances that may impact the management of corresponding resources.
Resource to gather: Prometheus and Alertmanager in all namespaces
apiVersion: monitoring.coreos.com/v1 kind: Prometheus
apiVersion: monitoring.coreos.com/v1 kind: Alertmanager
Backport: OCP 4.12.z; 4.13.z; 4.14.z; 4.15.z
Additional info:
1) Get the Prometheus and Alertmanager in all namespaces
$ oc get prometheus -A NAMESPACE NAME VERSION DESIRED READY RECONCILED AVAILABLE AGE openshift-monitoring k8s 2.39.1 2 1 True Degraded 712d test custom-prometheus 1 0 True False 25d
$ oc get alertmanager -A NAMESPACE NAME VERSION DESIRED READY RECONCILED AVAILABLE AGE openshift-monitoring main 2.39.1 2 1 True Degraded 712d test custom-alertmanager 1 0 True False 25d
- blocks
-
OCPBUGS-36380 [release4.14] Insights Operator to collect the 'prometheus' and 'alertmanager' instances
- Closed
- clones
-
OCPBUGS-34784 Insights Operator to collect the 'prometheus' and 'alertmanager' instances
- Closed
- is blocked by
-
OCPBUGS-35086 [release4.16] Insights Operator to collect the 'prometheus' and 'alertmanager' instances
- Closed
- is cloned by
-
OCPBUGS-36380 [release4.14] Insights Operator to collect the 'prometheus' and 'alertmanager' instances
- Closed
- links to
-
RHBA-2024:4151 OpenShift Container Platform 4.15.z bug fix update