Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OCPBUGS-42169: Bump k8s api to 1.28.14 #2091

Open
wants to merge 19 commits into
base: release-4.15
Choose a base branch
from

Conversation

jerpeter1
Copy link
Member

Bump kubernetes version to 1.28.14
/cc @bertinatto

wedaly and others added 19 commits August 14, 2024 11:50
Ensure kube-proxy waits for the services/endpointslices informer
caches to be synced *and* all pre-sync events delivered before
setting isInitialized=true. Otherwise, in clusters with many services,
some services may be missing from svcPortMap when kube-proxy starts
(e.g. during daemonset rollout). This can cause kube-proxy to temporarily
remove service DNAT rules and then skip cleanup of UDP conntrack entries
to a service VIP.

Resolves: kubernetes#126468
…pick-of-#126644-upstream-release-1.28

Automated cherry pick of kubernetes#126644: fix a scheduler preemption issue that victim is not patched
… cache and checking node topology distribution.
…ck-of-#125294-upstream-release-1.28

Automated cherry pick of kubernetes#125294: Add a new workqueue to endpointslice controller for updating
…k-of-#126532-upstream-release-1.28

Automated cherry pick of kubernetes#126532: kube-proxy: initialization wait for service and endpoint
[release-1.28] [go] Bump images, dependencies and versions to go 1.22.6 and distroless iptables
…pick-of-#126920-upstream-release-1.28

Automated cherry pick of kubernetes#126920: add missing RBAC to statefulset-controller for StatefulSetAutoDeletePVC feature
…k-of-#126240-kubernetes#126242-upstream-release-1.28

Automated cherry pick of kubernetes#126240: Update etcd from v3.5.14 to v3.5.15
kubernetes#126242: Build etcd image of v3.5.15
…herry-pick-of-#126343-upstream-release-1.28

Automated cherry pick of kubernetes#126343: Terminated pod should not be re-admitted
Kubernetes official release v1.28.14
@openshift-ci-robot openshift-ci-robot added the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Sep 20, 2024
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Sep 20, 2024
@openshift-ci-robot
Copy link

@jerpeter1: This pull request references Jira Issue OCPBUGS-42169, which is invalid:

  • expected the bug to target the "4.15.z" version, but no target version was set
  • 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-42169 to depend on a bug targeting a version in 4.16.0, 4.16.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), 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.

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

In response to this:

Bump kubernetes version to 1.28.14
/cc @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
Copy link

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

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci openshift-ci bot added vendor-update Touching vendor dir or related files approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Sep 20, 2024
@bertinatto
Copy link
Member

/retest-required

Copy link

openshift-ci bot commented Sep 20, 2024

@jerpeter1: all tests passed!

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.

Copy link
Member

@bertinatto bertinatto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I checked this by creating a separate branch, updating to Kubernetes 1.28.14 and comparing to this. The branches are an exact match.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 20, 2024
Copy link

openshift-ci bot commented Sep 20, 2024

[APPROVALNOTIFIER] This PR is APPROVED

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

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:

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. vendor-update Touching vendor dir or related files
Projects
None yet
Development

Successfully merging this pull request may close these issues.