OCPBUGS-48552: Update to Kubernetes 1.31.5

[atiratree]

/assign @bertinatto

[openshift-ci-robot]

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

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

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 are valid:

• 08daca6|UPSTREAM: 126750: Add takeByTopologyUnCoreCachePacked if policy option align-cpus-by-uncorecache is enabled. Adding new function to evaluate uncore cache id. Reverse allocation logic. Implement preferAlignByUncorecache within TakeByTopologyNUMAPacked, along with new test cases.: the upstream PR kubernetes/kubernetes#126750 has merged
• a2bc30e|UPSTREAM: 126750: update comments: the upstream PR kubernetes/kubernetes#126750 has merged

The following commits could not be validated and must be approved by a top-level approver:

• 04f5b20|kubelet: Fix the volume manager did't check the device mount state in the actual state of the world before marking the volume as detached. It may cause a pod to be stuck in the Terminating state due to the above issue when it was deleted.: does not specify an upstream backport in the commit message
• 1043bf3|Merge pull request #129494 from MadhavJivrajani/131-go124-webhook-regex-ut: does not specify an upstream backport in the commit message
• 11e2f11|Merge pull request #2163 from bertinatto/bump-1.31.4: does not specify an upstream backport in the commit message
• 1f83017|fetch cni plugins from GitHub releases: does not specify an upstream backport in the commit message
• 205ac00|Merge pull request #2144 from bertinatto/bump-v1.31.3-for-4.18: does not specify an upstream backport in the commit message
• 2b05163|UPSTREAM: : hack/update-vendor.sh, make update and update image: does not specify an upstream backport in the commit message
• 53c730c|UPSTREAM: : manually resolve conflicts: does not specify an upstream backport in the commit message
• 588d9d3|UPSTREAM: : hack/update-vendor.sh, make update and update image: does not specify an upstream backport in the commit message
• 5ac4d36|Merge pull request #129285 from ameukam/automated-cherry-pick-of-#129095-upstream-release-1.31: does not specify an upstream backport in the commit message
• 5d18fcd|UPSTREAM: : require configuration file enablement: does not specify an upstream backport in the commit message
• 6b42606|Merge tag 'v1.31.5' into bump-1.31.5: does not specify an upstream backport in the commit message
• 6f456a1|Merge pull request #129323 from ardaguclu/automated-cherry-pick-of-#129301-upstream-release-1.31: does not specify an upstream backport in the commit message
• 7164c72|Merge pull request #129062 from carlory/automated-cherry-pick-of-#128219-upstream-release-1.31: does not specify an upstream backport in the commit message
• 75c83a6|Merge pull request #129599 from aravindhp/automated-cherry-pick-of-#129595-upstream-release-1.31: does not specify an upstream backport in the commit message
• 774adff|webhook: alter regex to account for x509sha1 GODEBUG removal: 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
• 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
• a3cd81b|UPSTREAM: : Enable format library for 4.18: 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
• af64d83|Release commit for Kubernetes v1.31.5: does not specify an upstream backport in the commit message
• b26ab8b|Merge pull request #129454 from neolit123/automated-cherry-pick-of-#129452-origin-release-1.31-1735822759: does not specify an upstream backport in the commit message
• b555e6b|Fix volume expansion offline: 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
• b82572f|Do not attempt to truncate revision history if revisionHistoryLimit is negative: does not specify an upstream backport in the commit message
• b8265e7|prevent unnecessary resolving of iscsi/fc devices to dm: does not specify an upstream backport in the commit message
• c831762|Merge pull request #129181 from RomanBednar/automated-cherry-pick-of-#128086-upstream-release-1.31: does not specify an upstream backport in the commit message
• c94919d|kubelet: use env vars in node log query PS command: does not specify an upstream backport in the commit message
• c9ea8a4|Merge tag 'v1.31.3' into bump-v1.31.3-for-4.18: does not specify an upstream backport in the commit message
• cf36527|UPSTREAM: : manually resolve conflicts: 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
• d93c78a|Merge pull request #2162 from openshift-cherrypick-robot/cherry-pick-2136-to-release-4.18: does not specify an upstream backport in the commit message
• dad2757|Merge pull request #129235 from gnufied/automated-cherry-pick-of-#129085-upstream-release-1.31: does not specify an upstream backport in the commit message
• db71823|Merge pull request #2146 from openshift-cherrypick-robot/cherry-pick-2139-to-release-4.18: 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
• eb8c239|Bump images, dependencies and versions to go 1.22.10 and distroless iptables: does not specify an upstream backport in the commit message
• ec0d04b|Merge pull request #129424 from cpanato/update-go1234-rel131: does not specify an upstream backport in the commit message
• ec1a397|kubeadm: fix a bug where the node.skipPhases in UpgradeNodeConfiguration is not respected by 'kubeadm upgrade node': does not specify an upstream backport in the commit message
• fd78b52|Update CHANGELOG/CHANGELOG-1.31.md for v1.31.4: 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]

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

• expected dependent Jira Issue OCPBUGS-48553 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is Closed (Done) 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:

/assign @bertinatto

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]

[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

[atiratree]

Making sure the image change won't affect metal jobs. Please unhold if this is green.

Other than that, LGTM.

Thanks! Looks good.
/hold cancel
/jira refresh

[openshift-ci-robot]

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

• expected dependent Jira Issue OCPBUGS-48553 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is Closed (Done) 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:

Making sure the image change won't affect metal jobs. Please unhold if this is green.

Other than that, LGTM.

Thanks! Looks good.
/hold cancel
/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-48552, which is valid.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.18.0) matches configured target version for branch (4.18.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-48553 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
• dependent Jira Issue OCPBUGS-48553 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0
• bug has dependents

Requesting review from QA contact:
/cc @gangwgr

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.

[jrvaldes]

/test e2e-azure-ovn-upgrade

[kasturinarra]

/label cherry-pick-approved

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD e18ecb4 and 2 for PR HEAD d2d1c41 in total

[jrvaldes]

/test e2e-gcp

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 5f71ced and 1 for PR HEAD d2d1c41 in total

[openshift-ci-robot]

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

• openshift/kubernetes#2176

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

In response to this:

/assign @bertinatto

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-202502050631.p0.g071f77e.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-202502050631.p0.g071f77e.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-202502050631.p0.g071f77e.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-202502050631.p0.g071f77e.assembly.stream.el9.
All builds following this will include this PR.