Description of problem: The cluster network operator deploys a service monitor named "network-check-source" [1] which is never picked up by the cluster monitoring operator because the service monitor lives in the "openshift-network-diagnostics" namespace which doesn't have the 'openshift.io/cluster-monitoring="true"' label. Version-Release number of selected component (if applicable): 4.7 (probably) How reproducible: Always Steps to Reproduce: 1. Spin up a 4.7 cluster. 2. Query the "pod_network_connectivity_check_count" metric [3] in Prometheus. 3. Actual results: No result returned. Expected results: Some result returned. Additional info: [1] https://github.com/openshift/cluster-network-operator/blob/7498fab6bdc2b872c2f09e9a35eb19794a4c0fd7/bindata/network-diagnostics/network-check-source.yaml#L80-L101 [2] https://github.com/openshift/cluster-network-operator/blob/7498fab6bdc2b872c2f09e9a35eb19794a4c0fd7/bindata/network-diagnostics/000-ns.yaml#L1-L7 [3] https://github.com/openshift/cluster-network-operator/blob/7498fab6bdc2b872c2f09e9a35eb19794a4c0fd7/pkg/cmd/checkendpoints/controller/metrics.go#L22-L25
Additional information: I've noticed about it because this service monitor starts to show up in the user-workload Prometheus once you enable it.
Verified this bug on 4.9.0-0.nightly-2021-09-05-204238 Check "pod_network_connectivity_check_count" in console --> Observe -> Metrics Data can be found.
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 (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), 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/RHSA-2021:3759
*** Bug 2027290 has been marked as a duplicate of this bug. ***