OCPBUGS-18939: manifest: drop slo latency metrics in favor of sli

[dgrisonnet]

The apiserver_request_sli_duration_seconds metric was introduced as a
replacement of apiserver_request_slo_duration_seconds which is
deprecated in Kubernetes 1.27. This is just a renaming so besides
finding and replacing the name of the metrics no other action is
necessary.

To also avoid storing duplicated data in Prometheus, we need to drop
the apiserver_request_slo_duration_seconds at the ServiceMonitor level.

[openshift-ci-robot]

@dgrisonnet: This pull request references API-1523 which is a valid jira issue.

In response to this:

The apiserver_request_sli_duration_seconds metric was introduced as a
replacement of apiserver_request_slo_duration_seconds which is
deprecated in Kubernetes 1.27. This is just a renaming so besides
finding and replacing the name of the metrics no other action is
necessary.

To also avoid storing duplicated data in Prometheus, we need to drop
the apiserver_request_slo_duration_seconds at the ServiceMonitor level.

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/test-infra repository.

[openshift-ci-robot]

@dgrisonnet: This pull request references Jira Issue OCPBUGS-18939, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.15.0) matches configured target version for branch (4.15.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @wangke19

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

The apiserver_request_sli_duration_seconds metric was introduced as a
replacement of apiserver_request_slo_duration_seconds which is
deprecated in Kubernetes 1.27. This is just a renaming so besides
finding and replacing the name of the metrics no other action is
necessary.

To also avoid storing duplicated data in Prometheus, we need to drop
the apiserver_request_slo_duration_seconds at the ServiceMonitor level.

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/test-infra repository.

[wangke19]

@dgrisonnet Please review the test results https://issues.redhat.com/browse/OCPBUGS-18939?focusedId=23444263&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-23444263 after I pre-mrege verified the bug. Please confirm whether the result is as expected.

[dgrisonnet]

/retest-required

[wangke19]

pre-merge verified the associated bug, got the result is as expected. Detail see https://issues.redhat.com/browse/OCPBUGS-18939?focusedId=23729744&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-23729744.
/label qe-approved

[wangke19]

/retest-required

[openshift-ci-robot]

@dgrisonnet: This pull request references Jira Issue OCPBUGS-18939, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.16.0) matches configured target version for branch (4.16.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @wangke19

In response to this:

The apiserver_request_sli_duration_seconds metric was introduced as a
replacement of apiserver_request_slo_duration_seconds which is
deprecated in Kubernetes 1.27. This is just a renaming so besides
finding and replacing the name of the metrics no other action is
necessary.

To also avoid storing duplicated data in Prometheus, we need to drop
the apiserver_request_slo_duration_seconds at the ServiceMonitor level.

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.

[wangke19]

/retest

[wangke19]

/retest

[wangke19]

/test e2e-gcp-operator-single-node

[wangke19]

/test e2e-aws-operator-disruptive-single-node

[openshift-ci]

@dgrisonnet: 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-aws-operator-disruptive-single-node	9612e26	link	false	/test e2e-aws-operator-disruptive-single-node
ci/prow/e2e-gcp-operator-single-node	9612e26	link	false	/test e2e-gcp-operator-single-node

Full PR test history. Your PR dashboard.

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/test-infra repository. I understand the commands that are listed here.

[wangke19]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dgrisonnet, wangke19

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [dgrisonnet]

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

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 758ac1c and 2 for PR HEAD 9612e26 in total

[openshift-ci-robot]

@dgrisonnet: Jira Issue OCPBUGS-18939: Some pull requests linked via external trackers have merged:

The following pull requests linked via external trackers have not merged:

• openshift/cluster-authentication-operator#632 is open

These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

Jira Issue OCPBUGS-18939 has not been moved to the MODIFIED state.

In response to this:

The apiserver_request_sli_duration_seconds metric was introduced as a
replacement of apiserver_request_slo_duration_seconds which is
deprecated in Kubernetes 1.27. This is just a renaming so besides
finding and replacing the name of the metrics no other action is
necessary.

To also avoid storing duplicated data in Prometheus, we need to drop
the apiserver_request_slo_duration_seconds at the ServiceMonitor level.

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.