-
Notifications
You must be signed in to change notification settings - Fork 109
Update kubernetes dependencies to v1.34.0 #378
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
Conversation
Hi @dfajmon. Thanks for your PR. I'm waiting for a kubernetes-csi member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/ok-to-test |
5f38a907 Merge pull request kubernetes-csi#282 from rhrmo/update-go-1.24.6 579f6242 Update go to 1.24.6 74e066a8 Merge pull request kubernetes-csi#279 from Aishwarya-Hebbar/update-csi-prow-version 6f236be7 Update CSI prow driver version to v1.17.0 0ee55894 Merge pull request kubernetes-csi#280 from xing-yang/update_go_1.24.4 9af10153 update to go 1.24.4 f5fec3e3 Merge pull request kubernetes-csi#275 from chrishenzie/emeritus c5d285db Remove chrishenzie from kubernetes-csi-reviewers git-subtree-dir: release-tools git-subtree-split: 5f38a907597230563f5e2213aea116acdd9d86bc
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dfajmon, jsafrane 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 |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Update the release-tools subtree and bump all k8s dependencies to v1.34.0
Special notes for your reviewer:
cc @jsafrane
Does this PR introduce a user-facing change?: