OCPBUGS-29663: Update to kubernetes 1.26.14

[suleymanakbas91]

/assign @soltysh @jerpeter1

[openshift-ci-robot]

@suleymanakbas91: This pull request references Jira Issue OCPBUGS-29663, which is invalid:

• expected dependent Jira Issue OCPBUGS-29662 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is New 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 @soltysh @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]

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

• 2fc5586|Update CHANGELOG/CHANGELOG-1.26.md for v1.26.13: does not specify an upstream backport in the commit message
• 34fddee|Merge pull request #123062 from Richabanker/automated-cherry-pick-of-#122750-upstream-release-1.26: does not specify an upstream backport in the commit message
• 390799f|[go] Bump images, dependencies and versions to go 1.21.7 / distroless-iptables to v0.4.5: does not specify an upstream backport in the commit message
• 6db7980|Release commit for Kubernetes v1.26.14: does not specify an upstream backport in the commit message
• 7802e91|If a pvc has an empty storageclass name, don't try to assign a default StorageClass to it.: does not specify an upstream backport in the commit message
• 85ca651|Merge pull request #122858 from carlory/automated-cherry-pick-of-#122704-upstream-release-1.26: does not specify an upstream backport in the commit message
• d71cc23|UPSTREAM: : hack/update-vendor.sh, make update and update image: does not specify an upstream backport in the commit message
• d8b43d2|Add processStartTime in metrics/slis: does not specify an upstream backport in the commit message
• e0eeccd|Merge pull request #123230 from cpanato/update-go-126: does not specify an upstream backport in the commit message
• e88029c|Merge tag 'v1.26.14' into bump-1.26.14: 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.

[suleymanakbas91]

/retest

[suleymanakbas91]

/retest

[suleymanakbas91]

/test e2e-aws-ovn-cgroupsv2

[suleymanakbas91]

/test e2e-aws-ovn-cgroupsv2

[soltysh]

/lgtm
/approve

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

[openshift-ci]

@soltysh: Those labels are not set on the issue: backports/validated-commits

In response to this:

/lgtm
/approve

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

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/test-infra repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: soltysh, suleymanakbas91

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

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[soltysh]

/override ci/prow/verify-commits
this never passes on k8s bump

[openshift-ci]

@soltysh: Overrode contexts on behalf of soltysh: ci/prow/verify-commits

In response to this:

/override ci/prow/verify-commits
this never passes on k8s bump

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/test-infra repository.

[openshift-ci]

@suleymanakbas91: 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/verify-commits	d71cc23	link	true	/test verify-commits

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/test-infra repository. I understand the commands that are listed here.

[soltysh]

/label backports/validated-commits

[gangwgr]

/label cherry-pick-approved

[wallylewis]

/jira refresh

[openshift-ci-robot]

@wallylewis: This pull request references Jira Issue OCPBUGS-29663, which is invalid:

• expected dependent Jira Issue OCPBUGS-29662 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA 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.

[soltysh]

Manually overriding valid-bug since #1890 merged
/remove-label jira/invalid-bug
/label jira/valid-bug
/label backport-risk-assessed

[openshift-ci-robot]

@suleymanakbas91: Jira Issue OCPBUGS-29663: All pull requests linked via external trackers have merged:

• openshift/kubernetes#1889

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

In response to this:

/assign @soltysh @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-bot]

[ART PR BUILD NOTIFIER]

This PR has been included in build openshift-enterprise-pod-container-v4.13.0-202403081338.p0.g03ee898.assembly.stream.el8 for distgit openshift-enterprise-pod.
All builds following this will include this PR.

[openshift-merge-robot]

Fix included in accepted release 4.13.0-0.nightly-2024-03-08-182318