service and rule selectors removed

[obrienrobert]

Description

https://issues.redhat.com/browse/INTLY-3137?focusedCommentId=13820290&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-13820290

Once this is verified and merged, another PR will be created for the integreatly-operator which incorporates the removal of the monitoring-key label from individual resources.

Prerequisites

• Openshift 4.2 RHPDS cluster

Verification

• Login in to your cluster using oc login

• Run the Operator locally as per the instructions

• Once the operator is running, navigate to the Prometheus route in the application-monitoring namespace. The route should contain a single alert named - DeadMansSwitch

• Remove the monitoring-key: middle label from the above Prometheus rule:

  oc label prometheusrules prometheus-application-monitoring-rules monitoring-key- -n application -monitoring

• Allow a minute or 2 to pass, then verify that the DeadMansSwitch alert still exists in Prometheus.

[R-Lawton]

verifying now

[R-Lawton]

verification steps worked looks good to me

[david-martin]

@obrienrobert As discussed in person, lets go for the any: true approach as the serviceMonitorSelector and ruleSelector have to be set in order for prom operator to manage the config secret. The verification steps should probably be the same as what you did locally to test the values