Bug 1735509

Summary: monitor servicemonitors in openshift-kube-apiserver/openshift-kube-controller-manager/openshift-kube-scheduler are 0/0 up
Product: OpenShift Container Platform Reporter: Junqi Zhao <juzhao>
Component: kube-apiserverAssignee: David Eads <deads>
Status: CLOSED ERRATA QA Contact: Junqi Zhao <juzhao>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.2.0CC: alegrand, anpicker, aos-bugs, erooth, mfojtik, mloibl, pkrupa, sttts, surbania
Target Milestone: ---Keywords: Regression
Target Release: 4.3.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: two service monitor object were installed for each of kube-apiserver, kube-controller-manager and kube-scheduler, one named "monitor", the other one "kube-<apiserver|controller-manager|scheduler>". Consequence: The former object was inactive and showed an irritating "(0/0 up)" message. Fix: The former was inactive and is not created anymore in new clusters. Result: Only the cluster-kube-apiserver/kube-apiserver service monitor (and in analogy for the other two components) is created in new clusters.
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-01-23 11:04:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Description Flags
service discovery page none

Comment 1 Junqi Zhao 2019-08-01 02:53:38 UTC
Created attachment 1596849 [details]
service discovery page

Comment 7 errata-xmlrpc 2020-01-23 11:04:29 UTC
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, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.