-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
🌱 Upgrade to Kind v0.12.0 #6280
🌱 Upgrade to Kind v0.12.0 #6280
Conversation
Hi @DiptoChakrabarty. 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/test-infra repository. |
/ok-to-test |
Looks like you have to run There should be a few more Kubernetes (and thus kind) versions in docker.yaml which we should bump to the latest kind-published image versions |
update node version changes to versions rebase and version update
6ff7a67
to
2f3677f
Compare
Sorry missed the last push force notification somehow /lgtm /hold /assign @fabriziopandini |
/hold cancel |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fabriziopandini 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 |
/retitle 🌱 Upgrade to Kind v0.12.0 (just for release notes) |
What this PR does / why we need it: This updates to make use of latest kind v0.12.0 version
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #6264