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.

Sign up for GitHub

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

Jump to bottom

OCPBUGS-46003: Bump k8s api to 1.29.11 #2161

Open
wants to merge 16 commits into
base: release-4.16
Choose a base branch
from
Open

OCPBUGS-46003: Bump k8s api to 1.29.11 #2161

wants to merge 16 commits into from

Conversation

jerpeter1
Copy link
Member

Bump kubernetes version to 1.29.11
/cc @bertinatto

AxeZhan and others added 15 commits October 12, 2024 10:33
@AxeZhan
manually revert kubernetes#109877
c4a8184
@AxeZhan
tests for nodes with different nodeName and name
f2d5b1d
@k8s-release-robot
Update CHANGELOG/CHANGELOG-1.29.md for v1.29.10
0fadafe
@NoicFank
bugfix(scheduler): preemption picks wrong victim node with higher pri…
69066c2 
…ority pod on it.

Introducing pdb to preemption had disrupted the orderliness of pods in the victims,
which would leads picking wrong victim node with higher priority pod on it.
@p0lyn0mial
server/config: assing system:apiserver user to system:authenticated g…
994aaf9 
…roup
@k8s-ci-robot
Merge pull request kubernetes#128446 from p0lyn0mial/automated-cherry…
f2b2251 
…-pick-of-#127902-upstream-release-1.29

Automated cherry pick of kubernetes#127902: server/config: assing system:apiserver user to system:authenticated group
@bzsuni
Update etcd from v3.5.15 to v3.5.16
7aced6f 
Signed-off-by: bzsuni <[email protected]>
@bzsuni
Build etcd image v3.5.16
99b9064 
Signed-off-by: bzsuni <[email protected]>
@k8s-ci-robot
Merge pull request kubernetes#127951 from bzsuni/automated-cherry-pic…
c5ab4e3 
…k-of-#127285-kubernetes#127283-upstream-release-1.29

Automated cherry pick of kubernetes#127285: Update etcd from v3.5.15 to v3.5.16
kubernetes#127283: Build etcd image of v3.5.16
@k8s-ci-robot
Merge pull request kubernetes#127586 from AxeZhan/automated-cherry-pi…
4d73f6e 
…ck-of-#125398-upstream-release-1.29

Manually cherry pick of kubernetes#125398: [scheduler] When the hostname and nodename of a node do not match, ensure that pods carrying PVs with nodeAffinity are scheduled correctly.
@k8s-ci-robot
Merge pull request kubernetes#128435 from NoicFank/automated-cherry-p…
61cd265 
…ick-of-#128307-upstream-release-1.29

Automated cherry pick of kubernetes#128307: bugfix(scheduler): preemption picks wrong victim node with higher priority pod on it
@k8s-release-robot
Release commit for Kubernetes v1.29.11
960a2f0
@jerpeter1
Merge tag 'v1.29.11' into bump-1.29.11
b7303d4 
Kubernetes official release v1.29.11
@jerpeter1
UPSTREAM: <drop>: manually resolve conflicts
4cbf882
@jerpeter1
UPSTREAM: <drop>: hack/update-vendor.sh, make update and update image
8ca52ce
@openshift-ci-robot openshift-ci-robot added backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. 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 Dec 10, 2024
@openshift-ci-robot
Copy link

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

  • expected the bug to target the "4.16.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 dependent Jira Issue OCPBUGS-46002 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:

Bump kubernetes version to 1.29.11
/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 requested review from deads2k and tkashem December 10, 2024 21:19
@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 Dec 10, 2024
@bertinatto
Copy link
Member

/retest

@bertinatto
Copy link
Member

/test unit

@openshift-ci-robot
Copy link

@jerpeter1: the contents of this pull request could not be automatically validated.

The following commits are valid:

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.

bertinatto
bertinatto reviewed Dec 13, 2024
View reviewed changes
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.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 13, 2024
@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Dec 13, 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

@jerpeter1
Copy link
Member Author

/retest-required

2 similar comments
@jerpeter1
Copy link
Member Author

/retest-required

@jerpeter1
Copy link
Member Author

/retest-required

@jerpeter1
Copy link
Member Author

/test e2e-aws-ovn-serial

@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Dec 15, 2024

@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 699b059 link false /test e2e-agnostic-ovn-cmd
ci/prow/e2e-aws-ovn-serial 699b059 link true /test e2e-aws-ovn-serial

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@bertinatto bertinatto bertinatto left review comments

@deads2k deads2k Awaiting requested review from deads2k

@tkashem tkashem Awaiting requested review from tkashem

Assignees

@bertinatto bertinatto

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
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
10 participants
@jerpeter1 @openshift-ci-robot @bertinatto @AxeZhan @k8s-release-robot @NoicFank @p0lyn0mial @k8s-ci-robot @bzsuni @cpanato