TRT-2103: Revert "NO-JIRA: UPSTREAM: <carry>: Mark admissionregistration.k8s.io/v1beta1 as deprecated."

[xueqzhan]

Reverts #2287 tracked by TRT-2103

Per OpenShift policy, we are reverting this breaking change to get CI and/or nightly payloads flowing again.

4.20 nightly techpriew serial job failing with test:

[sig-arch][Late] clients should not use APIs that are removed in upcoming releases [apigroup:apiserver.openshift.io] [Suite:openshift/conformance/parallel]
{ fail [github.com/openshift/origin/test/extended/apiserver/api_requests.go:129]: user/system:serviceaccount:openshift-cluster-api:cluster-capi-operator accessed validatingadmissionpolicies.v1beta1.admissionregistration.k8s.io 2418 times
user/system:serviceaccount:openshift-cluster-api:cluster-capi-operator accessed validatingadmissionpolicybindings.v1beta1.admissionregistration.k8s.io 2418 times
Ginkgo exit error 1: exit with code 1}

Example job: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-ci-4.20-e2e-aws-ovn-techpreview/1920414382672580608

To unrevert this, revert this PR, and layer an additional separate commit on top that addresses the problem. Before merging the unrevert, please run these jobs on the PR and check the result of (job/X or job/X, test/Y tuple) to confirm the fix has corrected the problem:

/payload-job periodic-ci-openshift-release-master-ci-4.20-e2e-aws-ovn-techpreview

CC: @benluddy @JoelSpeed

[openshift-ci-robot]

@xueqzhan: This pull request references TRT-2103 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 bug to target the "4.20.0" version, but no target version was set.

Details

In response to this:

Reverts #2287 tracked by TRT-2103

Per OpenShift policy, we are reverting this breaking change to get CI and/or nightly payloads flowing again.

4.20 nightly techpriew serial job failing with test:

[sig-arch][Late] clients should not use APIs that are removed in upcoming releases [apigroup:apiserver.openshift.io] [Suite:openshift/conformance/parallel]
{ fail [github.com/openshift/origin/test/extended/apiserver/api_requests.go:129]: user/system:serviceaccount:openshift-cluster-api:cluster-capi-operator accessed validatingadmissionpolicies.v1beta1.admissionregistration.k8s.io 2418 times
user/system:serviceaccount:openshift-cluster-api:cluster-capi-operator accessed validatingadmissionpolicybindings.v1beta1.admissionregistration.k8s.io 2418 times
Ginkgo exit error 1: exit with code 1}

Example job: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-ci-4.20-e2e-aws-ovn-techpreview/1920414382672580608

To unrevert this, revert this PR, and layer an additional separate commit on top that addresses the problem. Before merging the unrevert, please run these jobs on the PR and check the result of (job/X or job/X, test/Y tuple) to confirm the fix has corrected the problem:

/payload-job periodic-ci-openshift-release-master-ci-4.20-e2e-aws-ovn-techpreview

CC: @benluddy @JoelSpeed

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]

@xueqzhan: 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:

• c07a842|Revert "NO-JIRA: UPSTREAM: : Mark admissionregistration.k8s.io/v1beta1 as deprecated.": 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.

[benluddy]

/lgtm

[xueqzhan]

/retest-required

[openshift-ci-robot]

@xueqzhan: 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:

• 0385d48|UPSTREAM: Revert "NO-JIRA: UPSTREAM: : Mark admissionregistration.k8s.io/v1beta1 as deprecated.": 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]

@xueqzhan: 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:

• 24bf6d5|UPSTREAM: : revert: NO-JIRA: UPSTREAM: : Mark admissionregistration.k8s.io/v1beta1 as deprecated.: 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.

[xueqzhan]

/skip

[benluddy]

/assign @bertinatto

[bertinatto]

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: benluddy, bertinatto, xueqzhan

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:

• DOWNSTREAM_OWNERS [benluddy,bertinatto]

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

[openshift-ci]

@xueqzhan: 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/okd-scos-e2e-aws-ovn	24bf6d5	link	false	/test okd-scos-e2e-aws-ovn
ci/prow/e2e-agnostic-ovn-cmd	24bf6d5	link	false	/test e2e-agnostic-ovn-cmd

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-bot]

[ART PR BUILD NOTIFIER]

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

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: kube-proxy
This PR has been included in build kube-proxy-container-v4.20.0-202505082342.p0.gc0af259.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.20.0-202505082342.p0.gc0af259.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.20.0-202505082342.p0.gc0af259.assembly.stream.el9.
All builds following this will include this PR.