OCPBUGS-56438: Update to Kubernetes v1.31.9

[atiratree]

No description provided.

[openshift-ci-robot]

@atiratree: This pull request references Jira Issue OCPBUGS-56438, which is invalid:

• expected Jira Issue OCPBUGS-56438 to depend on a bug targeting a version in 4.19.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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]

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

• 014728e|Check for newer fields when deciding expansion recovery feature status: does not specify an upstream backport in the commit message
• 356ae81|Merge pull request #131537 from ameukam/update-go-1-23-8-k8s-1-31: does not specify an upstream backport in the commit message
• 4370821|Also change final status by removing featuregate check: does not specify an upstream backport in the commit message
• 46a3947|Bump images, dependencies and versions: does not specify an upstream backport in the commit message
• 4d89057|Merge tag 'v1.31.9' into bump-1.31.9: does not specify an upstream backport in the commit message
• 5024972|Merge pull request #131429 from princepereira/automated-cherry-pick-of-#131138-upstream-release-1.31: does not specify an upstream backport in the commit message
• 772a0f4|Update CHANGELOG/CHANGELOG-1.31.md for v1.31.8: does not specify an upstream backport in the commit message
• 88e9d8f|Merge pull request #131439 from gnufied/automated-cherry-pick-of-#131418-upstream-release-1.31: does not specify an upstream backport in the commit message
• 8f04a31|UPSTREAM: : hack/update-vendor.sh, make update and update image: does not specify an upstream backport in the commit message
• 8f38003|Release commit for Kubernetes v1.31.9: does not specify an upstream backport in the commit message
• 92e3993|Manually adding fix for failing pull-kubernetes-typecheck tests which had dependency with this commit: https://github.com/kubernetes/kubernetes/commit/61863035803cc105619925a0fa23a779a9578bd4: does not specify an upstream backport in the commit message
• a1bb711|Fix for HNS local endpoint was being deleted instead of the remote endpoint.: does not specify an upstream backport in the commit message
• e4e7f31|Mark NodeExpansion finsihed without featuregate check: 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.

[atiratree]

/jira refresh

[openshift-ci-robot]

@atiratree: This pull request references Jira Issue OCPBUGS-56438, which is invalid:

• expected dependent Jira Issue OCPBUGS-56437 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
• expected dependent Jira Issue OCPBUGS-56437 to target a version in 4.19.0, but it targets "4.19.z" 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.

[bertinatto]

/remove-label backports/unvalidated-commits
/remove-label jira/invalid-bug
/label backports/validated-commits
/lgtm

[bertinatto]

/hold

Until 4.19 and 4.20 kube bumps merge.

[bertinatto]

/retest-required

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: atiratree, bertinatto

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

@atiratree: The following test 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	8f04a31	link	false	/test okd-scos-e2e-aws-ovn

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.

[bertinatto]

/hold

Until 4.19 and 4.20 kube bumps merge.

/hold cancel

[bertinatto]

/label backport-risk-assessed
/retest-required

[bertinatto]

/label jira/valid-bug

[xingxingxia]

/label cherry-pick-approved

[openshift-ci-robot]

@atiratree: Jira Issue OCPBUGS-56438: All pull requests linked via external trackers have merged:

• openshift/kubernetes#2307

Jira Issue OCPBUGS-56438 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-bot]

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-pod
This PR has been included in build openshift-enterprise-pod-container-v4.18.0-202505290235.p0.gaf5c163.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.18.0-202505290235.p0.gaf5c163.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-202505290235.p0.gaf5c163.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-202505290235.p0.gaf5c163.assembly.stream.el9.
All builds following this will include this PR.

[openshift-merge-robot]

Fix included in accepted release 4.18.0-0.nightly-2025-05-29-075806