MON-4129: revert https://github.com/openshift/cluster-kube-apiserver-operator/pull/1784

[machine424]

this also fixes a bad le="30(.0)?" as a result of #1742

The chosen approach is to move to float buckets one Prometheus v3 is merged forgetting about the integer historical data.

That will be done in #1816

[openshift-ci-robot]

@machine424: This pull request references MON-4129 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.19.0" version, but no target version was set.

Details

In response to this:

this also fixes a bad le="30(.0)?" as a result of #1742

The chosen approach is to move to float buckets one Prometheus v3 is merged forgetting about the integer historical data.

That will be done in #1816

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[vrutkovs]

/cc @dgrisonnet
/approve

[openshift-ci]

@machine424: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-gcp-operator-single-node	a730266	link	false	/test e2e-gcp-operator-single-node
ci/prow/e2e-aws-operator-disruptive-single-node	a730266	link	false	/test e2e-aws-operator-disruptive-single-node
ci/prow/e2e-aws-ovn-single-node	a730266	link	false	/test e2e-aws-ovn-single-node

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[openshift-ci]

@machine424: This PR was included in a payload test run from openshift/prometheus#227
trigger 15 job(s) of type blocking for the nightly release of OCP 4.19

• periodic-ci-openshift-release-master-ci-4.19-e2e-aws-upgrade-ovn-single-node
• periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn-upgrade
• periodic-ci-openshift-release-master-ci-4.19-e2e-azure-ovn-upgrade
• periodic-ci-openshift-release-master-ci-4.19-upgrade-from-stable-4.18-e2e-gcp-ovn-rt-upgrade
• periodic-ci-openshift-hypershift-release-4.19-periodics-e2e-aws-ovn-conformance
• periodic-ci-openshift-release-master-nightly-4.19-e2e-aws-ovn-serial
• periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn-techpreview
• periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn-techpreview-serial
• periodic-ci-openshift-release-master-nightly-4.19-e2e-aws-driver-toolkit
• periodic-ci-openshift-release-master-nightly-4.19-fips-payload-scan
• periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-ovn-bm
• periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-ovn-ipv6
• periodic-ci-openshift-microshift-release-4.19-periodics-e2e-aws-ovn-ocp-conformance
• periodic-ci-openshift-microshift-release-4.19-periodics-e2e-aws-ovn-ocp-conformance-serial
• periodic-ci-openshift-release-master-nightly-4.19-e2e-rosa-sts-ovn

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/bea89ed0-f4e3-11ef-876d-b67a60dab8dc-0

[openshift-ci]

@machine424: This PR was included in a payload test run from openshift/prometheus#227
trigger 4 job(s) of type blocking for the ci release of OCP 4.19

• periodic-ci-openshift-release-master-ci-4.19-upgrade-from-stable-4.18-e2e-aws-ovn-upgrade
• periodic-ci-openshift-release-master-ci-4.19-upgrade-from-stable-4.18-e2e-azure-ovn-upgrade
• periodic-ci-openshift-release-master-ci-4.19-e2e-gcp-ovn-upgrade
• periodic-ci-openshift-hypershift-release-4.19-periodics-e2e-aws-ovn

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/c8526010-f4e3-11ef-9e8c-0de34afca6c3-0

[dgrisonnet]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dgrisonnet, machine424, vrutkovs

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [dgrisonnet,vrutkovs]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment