OCPBUGS-46061: Update to Kubernetes 1.31.4

[bertinatto]

/assign @atiratree @jerpeter1

[openshift-ci-robot]

@bertinatto: This pull request references Jira Issue OCPBUGS-46061, which is invalid:

• expected the bug to target either version "4.19." or "openshift-4.19.", but it targets "4.17.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.

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

In response to this:

/assign @atiratree @jerpeter1

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]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[openshift-ci-robot]

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

• 3a81747|UPSTREAM: : hack/update-vendor.sh, make update and update image: does not specify an upstream backport in the commit message
• 779a082|Bump images, dependencies and versions to go 1.22.9 and distroless iptables: does not specify an upstream backport in the commit message
• 80964ef|fix isLikelyNotMountPointStatx relative path issue: does not specify an upstream backport in the commit message
• 953a3a8|Update CHANGELOG/CHANGELOG-1.31.md for v1.31.3: does not specify an upstream backport in the commit message
• 9968b8d|Merge pull request #129004 from andyzhangx/automated-cherry-pick-of-#128286-upstream-release-1.31: does not specify an upstream backport in the commit message
• a78aa47|Release commit for Kubernetes v1.31.4: does not specify an upstream backport in the commit message
• b73931a|Merge pull request #128806 from adrianmoisey/automated-cherry-pick-of-#128305-upstream-release-1.31: does not specify an upstream backport in the commit message
• d89400f|Merge pull request #128912 from cpanato/update-go-131: does not specify an upstream backport in the commit message
• e1d808c|Merge tag 'v1.31.4' into bump-1.31.4: does not specify an upstream backport in the commit message
• ea299ac|Ensure that a node's CIDR isn't released until the node is deleted: 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]

@bertinatto: This pull request references Jira Issue OCPBUGS-46061, which is invalid:

• expected the bug to target either version "4.18." or "openshift-4.18.", but it targets "4.17.z" instead
• 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-46061 to depend on a bug targeting a version in 4.19.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, 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.

In response to this:

/assign @atiratree @jerpeter1

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]

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

• 779a082|Bump images, dependencies and versions to go 1.22.9 and distroless iptables: does not specify an upstream backport in the commit message
• 7815f09|Merge tag 'v1.31.4' into bump-1.31.4: does not specify an upstream backport in the commit message
• 80964ef|fix isLikelyNotMountPointStatx relative path issue: does not specify an upstream backport in the commit message
• 953a3a8|Update CHANGELOG/CHANGELOG-1.31.md for v1.31.3: does not specify an upstream backport in the commit message
• 9968b8d|Merge pull request #129004 from andyzhangx/automated-cherry-pick-of-#128286-upstream-release-1.31: does not specify an upstream backport in the commit message
• a78aa47|Release commit for Kubernetes v1.31.4: does not specify an upstream backport in the commit message
• b73931a|Merge pull request #128806 from adrianmoisey/automated-cherry-pick-of-#128305-upstream-release-1.31: does not specify an upstream backport in the commit message
• d4eba92|UPSTREAM: : hack/update-vendor.sh, make update and update image: does not specify an upstream backport in the commit message
• d89400f|Merge pull request #128912 from cpanato/update-go-131: does not specify an upstream backport in the commit message
• ea299ac|Ensure that a node's CIDR isn't released until the node is deleted: 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]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 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

[bertinatto]

/retest

[openshift-ci]

@bertinatto: 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/e2e-aws-ovn-fips	d4eba92	link	true	/test e2e-aws-ovn-fips
ci/prow/e2e-azure-ovn-upgrade	d4eba92	link	true	/test e2e-azure-ovn-upgrade
ci/prow/e2e-aws-ovn-serial	d4eba92	link	true	/test e2e-aws-ovn-serial
ci/prow/e2e-aws-ovn-upgrade	d4eba92	link	true	/test e2e-aws-ovn-upgrade
ci/prow/e2e-aws-ovn-downgrade	d4eba92	link	true	/test e2e-aws-ovn-downgrade

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.