WRKLDS-1449: Update to Kubernetes v1.31.3

[bertinatto]

/assign @atiratree
/hold
should we merge after branch cut

[openshift-ci-robot]

@bertinatto: This pull request references WRKLDS-1449 which is a valid jira issue.

In response to this:

/assign @atiratree
/hold
should we merge after branch cut

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:

• 11d2b4d|Merge pull request #128340 from googs1025/automated-cherry-pick-of-#127834-upstream-release-1.31: does not specify an upstream backport in the commit message
• 19f244a|Merge pull request #128376 from mengjiao-liu/update-metrics-docs-1-31: does not specify an upstream backport in the commit message
• 1ef7d66|Update CHANGELOG/CHANGELOG-1.31.md for v1.31.2: does not specify an upstream backport in the commit message
• 247b4a9|UPSTREAM: : hack/update-vendor.sh, make update and update image: does not specify an upstream backport in the commit message
• 2d540ad|bugfix(scheduler): preemption picks wrong victim node with higher priority pod on it.: does not specify an upstream backport in the commit message
• 32286d5|server/config: assing system:apiserver user to system:authenticated group: does not specify an upstream backport in the commit message
• 6d1bcd7|Merge pull request #127928 from p0lyn0mial/automated-cherry-pick-of-#127902-upstream-release-1.31: does not specify an upstream backport in the commit message
• 7682b74|Fix TestCacherDontMissEventsOnReinitialization test: does not specify an upstream backport in the commit message
• 9624086|Update metrics documentation for v1.31: does not specify an upstream backport in the commit message
• 9865c0f|Merge tag 'v1.31.3' into bump-v1.31.3: does not specify an upstream backport in the commit message
• 9a5d6c5|UPSTREAM: : manually resolve conflicts: does not specify an upstream backport in the commit message
• c83cbee|Release commit for Kubernetes v1.31.3: does not specify an upstream backport in the commit message
• c94baac|fix(leaderelection): nil check in OnStoppedLeading func: does not specify an upstream backport in the commit message
• c9e75e7|Merge pull request #128236 from carlory/automated-cherry-pick-of-#128182-upstream-release-1.31: does not specify an upstream backport in the commit message
• d8d3194|tests for nodes with different nodeName and name: does not specify an upstream backport in the commit message
• dd898b8|Merge pull request #127584 from AxeZhan/automated-cherry-pick-of-#125398-upstream-release-1.31: does not specify an upstream backport in the commit message
• f6f4d80|Merge pull request #128530 from wojtek-t/automated-cherry-pick-of-#128468-upstream-release-1.31: does not specify an upstream backport in the commit message
• f7d6fad|Merge pull request #128431 from NoicFank/automated-cherry-pick-of-#128307-upstream-release-1.31: does not specify an upstream backport in the commit message
• fb63fe6|Fix crash on kube manager's service-lb-controller after v1.31.0.: does not specify an upstream backport in the commit message
• fdca80f|manually revert #109877: 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.

[bertinatto]

/retest

[atiratree]

Thanks for the update @bertinatto
/lgtm

branching has just been completed
/hold cancel

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

@bertinatto: This pull request references WRKLDS-1449 which is a valid jira issue.

In response to this:

/assign @atiratree
/hold
should we merge after branch cut

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
/label backports/validated-commits

[openshift-ci-robot]

@bertinatto: This pull request references WRKLDS-1449 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the epic to target either version "4.19." or "openshift-4.19.", but it targets "openshift-4.18" instead.

In response to this:

/assign @atiratree
/hold
should we merge after branch cut

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]

/retest-required

Remaining retests: 0 against base HEAD a3f31a4 and 2 for PR HEAD 247b4a9 in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD e3abfef and 2 for PR HEAD 247b4a9 in total

[bertinatto]

/test integration

{Failed;Failed;  I1126 04:57:14.405950   48876 factory.go:193] Registered Plugin "containerd"
I1126 04:57:14.412289   48876 etcd.go:71] etcd already running at http://127.0.0.1:2379
panic: test timed out after 10m0s
running tests:
	TestKMSv2Healthz (3m9s)

goroutine 171746 [running]:
testing.(*M).startAlarm.func1()
	/usr/lib/golang/src/testing/testing.go:2366 +0x385
created by time.goFunc
	/usr/lib/golang/src/time/sleep.go:177 +0x2d

goroutine 1 [chan receive, 3 minutes]:
testing.(*T).Run(0xc000afa1a0, {0x3f0f09f?, 0x0?}, 0x416feb0)
	/usr/lib/golang/src/testing/testing.go:1750 +0x3ab
testing.runTests.func1(0xc000afa1a0)
	/usr/lib/golang/src/testing/testing.go:2161 +0x37
testing.tRunner(0xc000afa1a0, 0xc000947b38)
	/usr/lib/golang/src/testing/testing.go:1689 +0xfb
testing.runTests(0xc000900bb8, {0x6a166c0, 0x11, 0x11}, {0x3e48e20?, 0xc000947bb8?, 0x6b6cf80?})
	/usr/lib/golang/src/testing/testing.go:2159 +0x445
testing.(*M).Run(0xc0003e1040)
	/usr/lib/golang/src/testing/testing.go:2027 +0x68b
k8s.io/kubernetes/test/integration/framework.EtcdMain(0xc000947f30)
	/go/src/k8s.io/kubernetes/test/integration/framework/etcd.go:224 +0x388
k8s.io/kubernetes/test/integration/controlplane/transformation.TestMain(...)
	/go/src/k8s.io/kubernetes/test/integration/controlplane/transformation/main_test.go:28
main.main()
	_testmain.go:93 +0x1be

[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-serial	247b4a9	link	true	/test e2e-aws-ovn-serial
ci/prow/e2e-agnostic-ovn-cmd	247b4a9	link	false	/test e2e-agnostic-ovn-cmd
ci/prow/e2e-azure-ovn-upgrade	247b4a9	link	true	/test e2e-azure-ovn-upgrade
ci/prow/k8s-e2e-conformance-aws	247b4a9	link	true	/test k8s-e2e-conformance-aws
ci/prow/e2e-aws-ovn-upgrade	247b4a9	link	true	/test e2e-aws-ovn-upgrade

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.

[openshift-bot]

[ART PR BUILD NOTIFIER]

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