OCPBUGS-39305: log only deprecated api requests

[sanchezl]

No description provided.

[openshift-ci-robot]

@sanchezl: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• da552a4|log only deprecated api requests: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@sanchezl: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• ebe3e35|log only deprecated api requests: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@sanchezl: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• d6dfede|log only deprecated api requests: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@sanchezl: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 15019c4|log only deprecated api requests: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@sanchezl: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 8a17248|log only deprecated api requests: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@sanchezl: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 1e508e8|log only deprecated api requests: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@sanchezl: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• b23ace3|log only deprecated api requests: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@sanchezl: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 21c86c2|log only deprecated api requests: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[wking]

New commits here have CI still running, but 15019c4 had some runs complete, and it already looks pretty good in terms of having fewer APIRequestCount resources in this presubmit run's must-gather:

$ curl -s https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openshift_kubernetes/2067/pull-ci-openshift-kubernetes-master-e2e-aws-ovn-serial/1828863952012972032/artifacts/e2e-aws-ovn-serial/gather-must-gather/artifacts/must-gather.tar | tar -tvz | grep apirequestcounts/
-rw------- 1003380000/root    6599 2024-08-28 15:09 registry-build03-ci-openshift-org-ci-op-rxqnq9yz-stable-sha256-18f723c850991a8c1bb9cfdd2b88323047bb24102fcddc248f7372ff4d117cca/cluster-scoped-resources/apiserver.openshift.io/apirequestcounts/flowschemas.v1beta1.flowcontrol.apiserver.k8s.io.yaml
-rw------- 1003380000/root    6615 2024-08-28 15:09 registry-build03-ci-openshift-org-ci-op-rxqnq9yz-stable-sha256-18f723c850991a8c1bb9cfdd2b88323047bb24102fcddc248f7372ff4d117cca/cluster-scoped-resources/apiserver.openshift.io/apirequestcounts/prioritylevelconfigurations.v1beta1.flowcontrol.apiserver.k8s.io.yaml

[openshift-ci-robot]

@sanchezl: This pull request references Jira Issue OCPBUGS-39305, which is invalid:

• expected the bug to target the "4.18.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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

In response to this:

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.

[openshift-ci-robot]

@sanchezl: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 30e2698|UPSTREAM: : log only deprecated api requests: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[dgrisonnet]

/lgtm
/approve

[tkashem]

/approve
/hold

(cancel at will)

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dgrisonnet, sanchezl, tkashem

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:

• DOWNSTREAM_OWNERS [tkashem]

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

[sanchezl]

/hold cancel

[openshift-ci]

@sanchezl: Can not set label backports/validated-commits: Must be member in one of these teams: [openshift-staff-engineers]

In response to this:

/remove-label backports/unvalidated-commits
/label backports/validated-commits

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.

[openshift-ci]

@sanchezl: Can not set label backports/unvalidated-commits: Must be member in one of these teams: [openshift-staff-engineers]

In response to this:

/remove-label backports/unvalidated-commits
/label backports/validated-commits

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.

[dinhxuanvu]

@bertinatto Would you mind taking a look and take care of the unvalidated comment label? Thanks.

[bertinatto]

Should this be squashed with 78c9d187348f?

If so (for the next ones), please use the same commit message so that we know this needs to be squashed.

/remove-label backports/unvalidated-commits
/label backports/validated-commits

[sanchezl]

/cherry-pick release-4.17 release-4.16

[openshift-cherrypick-robot]

@sanchezl: once the present PR merges, I will cherry-pick it on top of release-4.17 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.17 release-4.16

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.

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 8540bd4 and 2 for PR HEAD 205c34a in total

[openshift-ci]

@sanchezl: all tests passed!

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

[openshift-ci-robot]

@sanchezl: Jira Issue OCPBUGS-39305: All pull requests linked via external trackers have merged:

• openshift/kubernetes#2067

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

In response to this:

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.

[openshift-cherrypick-robot]

@sanchezl: new pull request created: #2111

In response to this:

/cherry-pick release-4.17 release-4.16

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.

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-pod
This PR has been included in build openshift-enterprise-pod-container-v4.18.0-202410150110.p0.g66f5c34.assembly.stream.el9.
All builds following this will include this PR.

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-hyperkube
This PR has been included in build openshift-enterprise-hyperkube-container-v4.18.0-202410150110.p0.g66f5c34.assembly.stream.el9.
All builds following this will include this PR.

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: ose-installer-kube-apiserver-artifacts
This PR has been included in build ose-installer-kube-apiserver-artifacts-container-v4.18.0-202410150110.p0.g66f5c34.assembly.stream.el9.
All builds following this will include this PR.