Skip to content

Commit

Permalink
PrometheusRules must reference monitoring.rhobs (#523)
Browse files Browse the repository at this point in the history
The PrometheusRules and editing must all reference the new
monitoring.rhobs CRD vs the old monitoring.coreos.com CRD which was
provided by the community Prometheus Operator (and potentially
conflicted with user-workload monitoring, and openshift-monitoring). All
references to PrometheusRules now refer to the monitoring.rhobs CRD and
any CLI commands are expanded for the full CRD path.
  • Loading branch information
leifmadsen authored Dec 5, 2023
1 parent 0e56add commit 36d54d1
Show file tree
Hide file tree
Showing 3 changed files with 3 additions and 3 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ You can add custom alerts to the `PrometheusRule` object that you created in xre
+
[source,bash]
----
$ oc edit prometheusrules prometheus-alarm-rules
$ oc edit prometheusrules.monitoring.rhobs prometheus-alarm-rules
----

. Edit the `PrometheusRules` manifest.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -70,7 +70,7 @@ $ oc project service-telemetry
[source,yaml]
----
$ oc apply -f - <<EOF
apiVersion: monitoring.coreos.com/v1
apiVersion: monitoring.rhobs/v1
kind: PrometheusRule
metadata:
creationTimestamp: null
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ $ oc project service-telemetry
[source,yaml,options="nowrap",role="white-space-pre"]
----
$ oc apply -f - <<EOF
apiVersion: monitoring.coreos.com/v1
apiVersion: monitoring.rhobs/v1
kind: PrometheusRule
metadata:
creationTimestamp: null
Expand Down

0 comments on commit 36d54d1

Please sign in to comment.