Description of problem: sum(sum_over_time(apiserver_request_count{group="extensions",version="v1beta1",resource!~"ingresses|",client!~"hyperkube/.*|cluster-policy-controller/.*"}[2d])) by (client, group, version, resource) {client="kubectl/v0.0.0 (linux/amd64) kubernetes/$Format",group="extensions",resource="deployments",version="v1beta1"} 320 {client="oc/v0.0.0 (linux/amd64) kubernetes/$Format",group="extensions",resource="deployments",version="v1beta1"} 84 {client="oc/v0.0.0 (linux/amd64) kubernetes/$Format",group="extensions",resource="daemonsets",version="v1beta1"} 1 {client="oc/v0.0.0 (linux/amd64) kubernetes/$Format",group="extensions",resource="replicasets",version="v1beta1"} 1 {client="openshift-tests/v1.16.2 (linux/amd64) kubernetes/8197733",group="extensions",resource="replicasets",version="v1beta1"} 790 Alerts will be fired as a result.
https://github.com/openshift/origin/pull/24089 merged moving to modified
Confirmed with payload: 4.3.0-0.nightly-2019-11-19-122017, when use prometheus could not see client="openshift-tests/v1.16.2 again. and could see alert from the webconsole: UsingDeprecatedAPIExtensionsV1Beta1 {client="oc/v0.0.0 (linux/amd64) kubernetes/$Format",group="extensions",resource="deployments",version="v1beta1"} 7296 {client="oc/v0.0.0 (linux/amd64) kubernetes/$Format",group="extensions",resource="daemonsets",version="v1beta1"} 1103
Was the alert firing before running the openshift-tests binary? If not I suspect the e2e can be running oc inside so the client wouldn't be indicative. But those are pretty high numbers, there might be IP in that data.
Nothing poped-up in the past days, based on the discussion I had with Tomas I'm moving this to 4.4
4.4 has disabled serving those, this should not be triggering anymore
Confirmed with payload: 4.4.0-0.nightly-2020-02-02-201619, after run the e2e test , can't see the alert anymore .
*** Bug 1806965 has been marked as a duplicate of this bug. ***
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:0581