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-49906: Bump k8s api to 1.29.13 #2199

Closed
wants to merge 28 commits into from

Conversation

jerpeter1
Copy link
Member

Bump kubernetes version to 1.29.13
/cc @bertinatto

k8s-release-robot and others added 27 commits November 20, 2024 14:03
[release-1.29][go] Bump images, dependencies and versions to go 1.22.9 and distroless iptables
… the actual state of the world before marking the volume as detached. It may cause a pod to be stuck in the Terminating state due to the above issue when it was deleted.
[release-1.29][go] Bump images, dependencies and versions to go 1.22.10 and distroless iptables
…ck-of-#129095-upstream-release-1.29

Automated cherry pick of kubernetes#129095: fetch cni plugins from GitHub releases
go1.24 removes the x509sha1 GODEBUG variable, and with it the
support for SHA-1 signed certs. This commit alters the regex
in unit tests to account for that and prep for go1.24.

Signed-off-by: Madhav Jivrajani <[email protected]>
…ck-of-#125040-upstream-release-1.29

Automated cherry pick of kubernetes#125040: Fix kubelet on Windows fails if a pod has SecurityContext with RunAsUser
…ck-of-#128219-upstream-release-1.29

Automated cherry pick of kubernetes#128219: kubelet: Fix the volume manager didn't check the device mount state in the actual state of the world before marking the volume as detached
…y-pick-of-#128086-upstream-release-1.29

Automated cherry pick of kubernetes#128086: prevent unnecessary resolving of iscsi/fc devices to dm
…pick-of-#129301-upstream-release-1.29

Automated cherry pick of kubernetes#129301: Do not attempt to truncate revision history if revisionHistoryLimit is negative
…ebhook-regex-ut

[go1.24][1.29] webhook: alter regex to account for x509sha1 GODEBUG removal
- Use environment variables to pass string arguments in the node log
  query PS command
- Split getLoggingCmd into getLoggingCmdEnv and getLoggingCmdArgs
  for better modularization
…pick-of-#129599-upstream-release-1.29

Automated cherry pick of kubernetes#129599: Automated cherry pick of kubernetes#129595: kubelet: use env vars in node log query PS command
Kubernetes official release v1.29.13
@openshift-ci openshift-ci bot requested a review from bertinatto February 6, 2025 01:21
@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. labels Feb 6, 2025
@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 Feb 6, 2025
@openshift-ci-robot
Copy link

@jerpeter1: This pull request references Jira Issue OCPBUGS-49906, 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-49905 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.13
/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 the vendor-update Touching vendor dir or related files label Feb 6, 2025
Copy link

openshift-ci bot commented Feb 6, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 6, 2025
@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.

Copy link

openshift-ci bot commented Feb 6, 2025

@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/k8s-e2e-aws-ovn-serial 9039022 link false /test k8s-e2e-aws-ovn-serial
ci/prow/e2e-aws-ovn-cgroupsv2 9039022 link true /test e2e-aws-ovn-cgroupsv2
ci/prow/verify-commits 9039022 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-sigs/prow repository. I understand the commands that are listed here.

}

args = append(args, fmt.Sprintf("--output=%s", output))

Copy link
Member

Choose a reason for hiding this comment

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

Reminder to follow the same approach as e25d066#r1944617492

@jerpeter1
Copy link
Member Author

Since, we're playing catch-up, I'm just going to drop this PR, and roll-up the changes in into the 1.29.14 PR.

@jerpeter1 jerpeter1 closed this Feb 18, 2025
@openshift-ci-robot
Copy link

@jerpeter1: This pull request references Jira Issue OCPBUGS-49906. The bug has been updated to no longer refer to the pull request using the external bug tracker. All external bug links have been closed. The bug has been moved to the NEW state.

In response to this:

Bump kubernetes version to 1.29.13
/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.

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. vendor-update Touching vendor dir or related files
Projects
None yet
Development

Successfully merging this pull request may close these issues.