Description of problem: The discovery of PodMonitors Custom Resource across namespaces is disabled. This prevents us to register those CusomResources in all 4.3.z openshift clusters. Version-Release number of selected component (if applicable): 4.3.z How reproducible: This is reproducible in any openshift 4.3.z cluster. Steps to Reproduce: 1. Create PodMonitor in a user namespace Actual results: Prometheus `fails` to discover/register the target in the same way as ServiceMonitor does. Expected results: Prometheus `should` discover/register the target. Additional info: Potential fix in this PR: https://github.com/coreos/kube-prometheus/pull/317
@damien: just fyi, we need to fix in 4.5.0 (master) first, then we can decide for backports. I can show you the process how it works, it is a bit involved. I suggest we backport to 4.4. as an exercise, that should be good enough :-)
The fix is already in 4.4 and 4.5 https://github.com/openshift/cluster-monitoring-operator/blob/master/assets/prometheus-user-workload/prometheus.yaml#L83 If that does not work, then its a separate bug.
In that case marking as MODIFIED for verification, I will also create a clone for 4.4 in MODIFIED state too and a 4.3 clone in POST state referencing the PR.
Tested with 4.5.0-0.nightly-2020-03-12-172608,and create PodMonitor in a user namespace, Prometheus can discover/register the target
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.5 image release advisory), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2409