OCPBUGS-21100: bump k8s.io (release-4.14)

[ibihim]

What

Bump k8s.io & Co deps

Why

Fix HTTP/2 issues

Ref

#98

[ibihim]

/retest-required

[openshift-ci]

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

[stlaz]

/lgtm

[stlaz]

/label backport-risk-assessed

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ibihim, stlaz

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 [stlaz]

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

[dpuniaredhat]

/label qe-approved

[dpuniaredhat]

/label cherry-pick-approved

[openshift-ci-robot]

@ibihim: This pull request references Jira Issue OCPBUGS-21100, which is invalid:

• expected dependent Jira Issue OCPBUGS-21669 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

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:

What

Bump k8s.io & Co deps

Why

Fix HTTP/2 issues

Ref

#98

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.

[stlaz]

/jira refresh

[openshift-ci-robot]

@stlaz: This pull request references Jira Issue OCPBUGS-21100, which is invalid:

• expected dependent Jira Issue OCPBUGS-21669 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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.

In response to this:

/jira refresh

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.

[dpuniaredhat]

/remove-label cherry-pick-approved

[stlaz]

/jira refresh

[openshift-ci-robot]

@stlaz: This pull request references Jira Issue OCPBUGS-21100, which is invalid:

• expected dependent Jira Issue OCPBUGS-21669 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ASSIGNED instead

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.

In response to this:

/jira refresh

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.

[ibihim]

/jira refresh

[openshift-ci-robot]

@ibihim: This pull request references Jira Issue OCPBUGS-21100, which is valid.

6 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.14.z) matches configured target version for branch (4.14.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• dependent bug Jira Issue OCPBUGS-21669 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-21669 targets the "4.15.0" version, which is one of the valid target versions: 4.15.0
• bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (dpunia@redhat.com), skipping review request.

In response to this:

/jira refresh

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.

[dpuniaredhat]

/label cherry-pick-approved

[openshift-ci-robot]

@ibihim: Jira Issue OCPBUGS-21100: All pull requests linked via external trackers have merged:

• openshift/oauth-apiserver#100

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

In response to this:

What

Bump k8s.io & Co deps

Why

Fix HTTP/2 issues

Ref

#98

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

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-oauth-apiserver-container-v4.14.0-202402081039.p0.g8f5c90c.assembly.stream.el8 for distgit ose-oauth-apiserver.
All builds following this will include this PR.

[openshift-merge-robot]

Fix included in accepted release 4.14.0-0.nightly-2024-02-10-003038