OCPBUGS-55267: Update to Kubernetes v1.31.8

[atiratree]

No description provided.

[openshift-ci-robot]

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

• expected the bug to target the "4.18.z" version, but no target version was set
• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected Jira Issue OCPBUGS-55267 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:

• 3836d58|fix handle terminating pvc when kubelet rebuild dsw: does not specify an upstream backport in the commit message
• 3a67945|Merge pull request #130685 from carlory/automated-cherry-pick-of-#130335-upstream-release-1.31: does not specify an upstream backport in the commit message
• 3f46d43|Release commit for Kubernetes v1.31.8: does not specify an upstream backport in the commit message
• 5a354ec|Merge tag 'v1.31.8' into bump-1.31.8: does not specify an upstream backport in the commit message
• 6ed5abc|Merge pull request #131160 from wojtek-t/automated-cherry-pick-of-#131020-upstream-release-1.31: does not specify an upstream backport in the commit message
• 77de0b9|fix e2e: does not specify an upstream backport in the commit message
• ab4389f|add e2e test to reproduce unexpected unmount after kubelet is restarted: does not specify an upstream backport in the commit message
• b9e1dc6|UPSTREAM: : hack/update-vendor.sh, make update and update image: does not specify an upstream backport in the commit message
• de2117a|Fix race for sending errors in watch: does not specify an upstream backport in the commit message
• de93867|Update CHANGELOG/CHANGELOG-1.31.md for v1.31.7: 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-55267, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected dependent Jira Issue OCPBUGS-55265 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
• expected dependent Jira Issue OCPBUGS-55265 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.

[atiratree]

/jira refresh

[openshift-ci-robot]

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

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected dependent Jira Issue OCPBUGS-55265 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.

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.

[atiratree]

/jira refresh

[openshift-ci-robot]

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

• expected dependent Jira Issue OCPBUGS-55265 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.

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.

[atiratree]

/retest

[atiratree]

/test e2e-aws-ovn-serial

[openshift-ci]

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

[bertinatto]

/label jira/valid-bug
/remove-label jira/invalid-bug
/label backport-risk-assessed
/lgtm

[bertinatto]

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

[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

[xingxingxia]

/label cherry-pick-approved

[openshift-ci-robot]

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

• openshift/kubernetes#2278

Jira Issue OCPBUGS-55267 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: kube-proxy
This PR has been included in build kube-proxy-container-v4.18.0-202505060638.p0.gaf98ede.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-202505060638.p0.gaf98ede.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-202505060638.p0.gaf98ede.assembly.stream.el9.
All builds following this will include this PR.

[openshift-bot]

[ART PR BUILD NOTIFIER]

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