This bug was initially created as a copy of Bug #1764313 I am copying this bug because: metrics for the kube-apiserver include critical metrics for determining pieces of cluster configuration and state back through telemetry. it's also the generic mechanism used by many other operators. found by service catalog and console who have each tried to shim around the problem. The /metrics endpoint should have an e2e test to validate that it responds with prometheus metrics. The key metrics is console_url. The console operator is not currently reporting console_url on master (4.3).
https://github.com/openshift/library-go/pull/584
*** Bug 1766518 has been marked as a duplicate of this bug. ***
*** Bug 1770381 has been marked as a duplicate of this bug. ***
Ying Zhou, please help verify this bug, thanks.
Confirmed with latest payload 4.3.0-0.nightly-2019-11-26-171052, the issue has fixed: 1. oc edit FeatureGate cluster # add below and save ... spec: featureSet: "TechPreviewNoUpgrade" 2. TK=`oc sa get-token cluster-monitoring-operator -n openshift-monitoring` [root@dhcp-140-138 ~]# oc get ep -n openshift-kube-apiserver-operator NAME ENDPOINTS AGE metrics 10.128.0.8:8443 5h8m [root@dhcp-140-138 ~]# oc get po -n openshift-kube-apiserver-operator NAME READY STATUS RESTARTS AGE kube-apiserver-operator-b76fc9c88-cv7lk 1/1 Running 2 5h8m 3. [root@dhcp-140-138 ~]# oc exec kube-apiserver-operator-b76fc9c88-cv7lk -- curl -k -H "Authorization: Bearer $token" https://10.128.0.8:8443/metrics > /tmp/metrics % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 96849 0 96849 0 0 663k 0 --:--:-- --:--:-- --:--:-- 666k [root@dhcp-140-138 ~]# cat /tmp/metrics |grep featu # HELP cluster_feature_set Reports the feature set the cluster is configured to expose. name corresponds to the featureSet field of the cluster. The value is 1 if a cloud provider is supported. # TYPE cluster_feature_set gauge cluster_feature_set{name="TechPreviewNoUpgrade"} 0
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-2020:0062