OCPBUGS-32309: Bump K8s api to 1.27.13

[jerpeter1]

/assign @soltysh

[openshift-ci-robot]

@jerpeter1: This pull request references Jira Issue OCPBUGS-32309, 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"
• expected dependent Jira Issue OCPBUGS-32299 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

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]

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

• 017248f|Serve watch without resourceVersion from cache and introduce a WatchFromStorageWithoutResourceVersion feature gate to allow serving watch from storage.: does not specify an upstream backport in the commit message
• 127fa02|Merge pull request #124129 from carlory/automated-cherry-pick-of-#124124-upstream-release-1.27: does not specify an upstream backport in the commit message
• 1a7ed95|Merge pull request #122679 from bmwiedemann/automated-cherry-pick-of-#121894-origin-release-1.27: does not specify an upstream backport in the commit message
• 2f0c6b7|UPSTREAM: : hack/update-vendor.sh, make update and update image: does not specify an upstream backport in the commit message
• 310d3db|hack/tools: bump honnef.co/go/tools to v0.4.6: does not specify an upstream backport in the commit message
• 3f09225|Add envFrom to serviceaccount admission plugin: does not specify an upstream backport in the commit message
• 441edd5|build: use -trimpath in non-DBG mode: does not specify an upstream backport in the commit message
• 49dcf18|Merge pull request #124142 from bertinatto/automated-cherry-pick-of-#124048-upstream-release-1.27: does not specify an upstream backport in the commit message
• 55f2f35|UPSTREAM: : manually resolve conflicts: does not specify an upstream backport in the commit message
• 63758cc|Merge tag 'v1.27.13' into bump-1.27.13: does not specify an upstream backport in the commit message
• 6ec93a8|Merge pull request #123769 from pohly/release-1.27-go-tools-0.4.6: does not specify an upstream backport in the commit message
• 7840458|Use DBG=1 for conformance verification: does not specify an upstream backport in the commit message
• 7c861b1|Merge pull request #124325 from ritazh/automated-cherry-pick-of-#124322-upstream-release-1.27: does not specify an upstream backport in the commit message
• 8be2458|Merge pull request #124199 from cpanato/update-go-1.27: does not specify an upstream backport in the commit message
• 942249c|Use the right feature gate when updating uncertain volumes: does not specify an upstream backport in the commit message
• 96b450c|Release commit for Kubernetes v1.27.13: does not specify an upstream backport in the commit message
• a934b62|[go] Bump images, dependencies and versions to go 1.21.9 and distroless iptables: does not specify an upstream backport in the commit message
• adf10d3|[CVE-2023-45288] .*: bump x/net to v0.23.0: does not specify an upstream backport in the commit message
• beaf10e|Merge pull request #124007 from serathius/consistent-watch-from-etcd-1.27: does not specify an upstream backport in the commit message
• bfd9892|fix panic with SIGSEGV in kubeadm certs check-expiration: does not specify an upstream backport in the commit message
• c37a819|Update CHANGELOG/CHANGELOG-1.27.md for v1.27.12: does not specify an upstream backport in the commit message
• e8b9250|Merge pull request #124178 from MadhavJivrajani/bump-x-net-2023-45288-127: 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.

[wangke19]

/test e2e-agnostic-ovn-cmd

[soltysh]

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

[soltysh]

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

[soltysh]

/label backport-risk-assessed
Since #1946 merged, I'm manually overriding jira labels
/remove-label jira/invalid-bug
/label jira/valid-bug

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

@jerpeter1: 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-agnostic-ovn-cmd	960dc45	link	false	/test e2e-agnostic-ovn-cmd
ci/prow/verify-commits	960dc45	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.

[wangke19]

/label cherry-pick-approved

[soltysh]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

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

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

[openshift-ci-robot]

@jerpeter1: Jira Issue OCPBUGS-32309: All pull requests linked via external trackers have merged:

• openshift/kubernetes#1950

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

In response to this:

/assign @soltysh

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.14.0-202404231437.p0.g401bb48.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.14.0-0.nightly-2024-04-24-075532

[wangke19]

/jira refresh

[openshift-ci-robot]

@wangke19: Jira Issue OCPBUGS-32309 is in an unrecognized state (Verified) and will not be moved to the MODIFIED state.

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.