Description of problem: kube 1.16 disabled serving extensions/v1beta1 (except ingress) and with the rebase we have temporary enabled it back for this release and we are adding an alert to warn on using the deprecated apis. Serving will be disabled in the next release. OCM needs to migrate to apps/v1 ASAP. Element Value apiserver_request_count{client="openshift-controller-manager/v0.0.0 (linux/amd64) kubernetes/$Format",code="0",component="apiserver",contentType="application/vnd.kubernetes.protobuf;stream=watch",endpoint="https",group="extensions",instance="10.0.134.26:6443",job="apiserver",namespace="default",resource="daemonsets",scope="cluster",service="kubernetes",verb="WATCH",version="v1beta1"} 31 apiserver_request_count{client="openshift-controller-manager/v0.0.0 (linux/amd64) kubernetes/$Format",code="0",component="apiserver",contentType="application/vnd.kubernetes.protobuf;stream=watch",endpoint="https",group="extensions",instance="10.0.134.26:6443",job="apiserver",namespace="default",resource="deployments",scope="cluster",service="kubernetes",verb="WATCH",version="v1beta1"} 31 apiserver_request_count{client="openshift-controller-manager/v0.0.0 (linux/amd64) kubernetes/$Format",code="0",component="apiserver",contentType="application/vnd.kubernetes.protobuf;stream=watch",endpoint="https",group="extensions",instance="10.0.134.26:6443",job="apiserver",namespace="default",resource="replicasets",scope="cluster",service="kubernetes",verb="WATCH",version="v1beta1"} 29 apiserver_request_count{client="openshift-controller-manager/v0.0.0 (linux/amd64) kubernetes/$Format",code="200",component="apiserver",contentType="application/vnd.kubernetes.protobuf",endpoint="https",group="extensions",instance="10.0.134.26:6443",job="apiserver",namespace="default",resource="daemonsets",scope="cluster",service="kubernetes",verb="LIST",version="v1beta1"} 1 apiserver_request_count{client="openshift-controller-manager/v0.0.0 (linux/amd64) kubernetes/$Format",code="200",component="apiserver",contentType="application/vnd.kubernetes.protobuf",endpoint="https",group="extensions",instance="10.0.134.26:6443",job="apiserver",namespace="default",resource="replicasets",scope="cluster",service="kubernetes",verb="LIST",version="v1beta1"} 1 Version-Release number of selected component (if applicable): oc version Client Version: version.Info{Major:"", Minor:"", GitVersion:"v4.2.0-alpha.0-56-ge6a379d", GitCommit:"e6a379d50", GitTreeState:"clean", BuildDate:"2019-09-05T10:19:53Z", GoVersion:"go1.13", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"16+", GitVersion:"v1.16.0-beta.2+03b33d2", GitCommit:"03b33d2", GitTreeState:"clean", BuildDate:"2019-10-21T19:38:32Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"} OpenShift Version: 4.3.0-0.ci-2019-10-22-062243
This is a release blocker, we cannot deliver w/o this being fixed ASAP. We have alerts in place which will be triggered every time deprecated API is being used. This alert should not apply to any resources provided by OpenShift itself but should serve customers as an information that in the next version these API won't be available.
This seems to be fixed already, I have a cluster running for a couple of hours with no output when querying Prometheus for such metrics(exception made for resource="ingresses" as expected).
For the record: sum(apiserver_request_count{client=~"openshift-controller-manager.*",version=~"v1beta.*"}) by (group,resource) {group="batch",resource="cronjobs"} 8 {group="extensions",resource="ingresses"} 7 {group="authentication.k8s.io",resource="tokenreviews"} 28 {group="authorization.k8s.io",resource="subjectaccessreviews"} 28
Verified in version: 4.3.0-0.nightly-2019-10-29-140935 --In 4.2 record: sum(apiserver_request_count{client=~"openshift-controller-manager.*",version=~"v1beta.*"}) by (group,resource) {group="batch",resource="cronjobs"} 9 {group="events.k8s.io",resource="events"} 8 {group="extensions",resource="daemonsets"} 6 {group="extensions",resource="replicasets"} 7 {group="policy",resource="poddisruptionbudgets"} 9 {group="authorization.k8s.io",resource="subjectaccessreviews"} 34 {group="apps",resource="statefulsets"} 10 {group="extensions",resource="deployments"} 8 {group="extensions",resource="ingresses"} 9 {group="networking.k8s.io",resource="ingresses"} 8 {group="authentication.k8s.io",resource="tokenreviews"} 34 --In 4.3 version above, daemonsets, deployments and replicasets already update api. {group="batch",resource="cronjobs"} 41 {group="extensions",resource="ingresses"} 41 {group="authentication.k8s.io",resource="tokenreviews"} 168 {group="authorization.k8s.io",resource="subjectaccessreviews"} 168
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