Master scheduling is a key variant of cluster config that can lead to user failure and is also required to properly account for subscription information per cluster. A metric on the cluster needs to report whether master schedulable is true and that needs to come back via telemetry. The metric might look like # masters are schedulable cluster_master_schedulable 1 # masters are not schedulable cluster_master_schedulable 0 Must be in 4.2 so we can properly count subscription data.
PR: https://github.com/openshift/cluster-kube-scheduler-operator/pull/168
Failed to verify with 4.2.0-0.nightly-2019-09-11-202233, open console, search "cluster_master_schedulable" in "Insert Metric at Cursor", there is not this item, feel free to contact with me if there is misunderstanding. thx
no, checked with 4.2.0-0.nightly-2019-09-15-221449, still have not fix.
Created attachment 1618351 [details] cluster-master-schedulable Looking today I am able to see the cluster-master-schedulable metric on a running cluster (4.2.0-0.ci-2019-09-23-093016)
Verified with 4.2.0-0.nightly-2019-09-24-025718 cluster_master_schedulable https 10.129.0.11:8443 metrics openshift-kube-scheduler-operator openshift-kube-scheduler-operator-757465cc56-g8btl metrics
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. https://access.redhat.com/errata/RHBA-2019:2922