-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
[kubernetes] Add hashes for kubernetes 1.30 (#11109) #11261
[kubernetes] Add hashes for kubernetes 1.30 (#11109) #11261
Conversation
Hi @tmurakam. Thanks for your PR. I'm waiting for a kubernetes-sigs 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 |
/retest |
@tmurakam, could you rebase this PR to fix the CI? |
be5e61e
to
7e4d7a7
Compare
/lgtm |
Add hashes to crictl, crio, kubelet, kubectl and kubeadm
7e4d7a7
to
7e21430
Compare
Added hashes for kubernetes 1.30.2. |
/retest-failed |
/lgtm |
Any ETAs of when this is going to be merged? |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mzaian, tmurakam 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 |
Add hashes to crictl, crio, kubelet, kubectl and kubeadm for Kubernetes 1.30.0 and 1.30.1.
What type of PR is this?
/kind feature
What this PR does / why we need it:
Add hashes to crictl, crio, kubelet, kubectl and kubeadm for #11109.
I used the download_hash.sh to get hashes.
This does not change default kubernetes version.
Does this PR introduce a user-facing change?: