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-39015: Bump k8s api to 1.29.8 #2066

Merged
merged 28 commits into from
Sep 6, 2024

Conversation

sairameshv
Copy link
Member

Bump kubernetes version to 1.29.8

/cc @soltysh

mimowo and others added 25 commits July 12, 2024 19:28
For request like '/api/v1/watch/namespaces/*', don't set scope.namespace.
Because the func `addWatcher` add a watcher to allWatchers with the value `scope.namespace` not empty.
But the function `dispatchEvent` dispatch event with an empty namespace.

Signed-off-by: xyz-li <hui0787411@163.com>
This change make api-server not omity the field `item` of
ValidatingAdmissionPolicyList when ValidatingAdmissionPolicy is empty.
So kubetl will print ValidatingAdmissionPolicyList correctly when ValidatingAdmissionPolicy is empty.

Signed-off-by: xyz-li <hui0787411@163.com>
…k-of-#125404-upstream-release-1.29

Automated cherry pick of kubernetes#125404: Fix that PodIP field is not set for terminal pod
…k-of-#126046-upstream-release-1.29

Automated cherry pick of kubernetes#126046: Use omitempty for optional fields in Job Pod Failure Policy
cherry-pick update gpu driver installer for release 1.29
This ensures that the restartable init containers receive a termination
signal even if there are any not-started restartable init containers, by
ignoring the not-running containers.
…-pick-of-#126174-upstream-release-1.29

Automated cherry pick of kubernetes#126174: mount-utils: treat syscall.ENODEV as corrupted mount
Cherry pick of kubernetes#124568 fix ValidatingAdmissionPolicyList json tag
…ck-of-#125935-upstream-release-1.29

Automated cherry pick of kubernetes#125935: Terminate restartable init containers ignoring not-started containers
…k-of-#126167-upstream-release-1.29

Automated cherry pick of kubernetes#126167: Hot fix for panic on schema conversion.
Respect controllers on PVCs for retention policy
…ick-of-#126012-upstream-release-1.29

Automated cherry pick of kubernetes#126012: Updating kubelet on Windows to query uuid from registry
Kubernetes official release v1.29.8
@openshift-ci-robot openshift-ci-robot added the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Aug 28, 2024
@openshift-ci openshift-ci bot requested a review from soltysh August 28, 2024 11:19
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 28, 2024
@openshift-ci-robot
Copy link

@sairameshv: This pull request references Jira Issue OCPBUGS-39015, which is invalid:

  • expected dependent Jira Issue OCPBUGS-39014 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.8

/cc @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 openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Aug 28, 2024
@openshift-ci openshift-ci bot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Sep 5, 2024
@jerpeter1
Copy link
Member

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Sep 5, 2024
@jerpeter1
Copy link
Member

/approve

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 5, 2024
@jerpeter1
Copy link
Member

/lgtm

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

openshift-ci bot commented Sep 5, 2024

[APPROVALNOTIFIER] This PR is APPROVED

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

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

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

@openshift-ci openshift-ci bot added backports/validated-commits Indicates that all commits come to merged upstream PRs. and removed backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. labels Sep 5, 2024
@jerpeter1
Copy link
Member

/retest-required

1 similar comment
@jerpeter1
Copy link
Member

/retest-required

Copy link

openshift-ci bot commented Sep 5, 2024

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

@jerpeter1
Copy link
Member

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Sep 6, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit f10c92d into openshift:release-4.16 Sep 6, 2024
23 checks passed
@openshift-ci-robot
Copy link

@sairameshv: Jira Issue OCPBUGS-39015: All pull requests linked via external trackers have merged:

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

In response to this:

Bump kubernetes version to 1.29.8

/cc @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
Copy link

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-pod
This PR has been included in build openshift-enterprise-pod-container-v4.16.0-202409060210.p0.gf10c92d.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-hyperkube
This PR has been included in build openshift-enterprise-hyperkube-container-v4.16.0-202409060210.p0.gf10c92d.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

Distgit: ose-installer-kube-apiserver-artifacts
This PR has been included in build ose-installer-kube-apiserver-artifacts-container-v4.16.0-202409060210.p0.gf10c92d.assembly.stream.el9.
All builds following this will include this PR.

@openshift-merge-robot
Copy link

Fix included in accepted release 4.16.0-0.nightly-2024-09-06-124228

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. backports/validated-commits Indicates that all commits come to merged upstream PRs. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/valid-bug Indicates that a referenced Jira bug is valid 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.