Since we will pursue the prometheus-operator with group rename approach for OBO, this prometheus-operator deployment will not react to coreos resources, like servicemonitors.monitoring.coreos.com. It will instead only watch for servicemonitors.rhobs.monitoring. Only renaming the group of some resources was deemed too brittle ad complex to carry as a downstream change.

This task serves two purposes:

1. Determine if OBO stakeholder can switch their monitoring configurations to the new group names or if they will need OBO to support the original resource groups (and which exactly)
2. Track the implementation in OBO to support the needed coreos group resources. The assumption is that OBO will only need to support a subset of all coreos resources. Typically this will include resources that are aimed at users to configure what to monitor and some monitoring assets.

If any stakeholder needs OBO to support some coreos resources we assume the following will suffice initially:

• ServiceMonitor
• PodMonitor
• PrometheusRule