cluster kind: update kind-1.23 to kind-1.27

[zhlhahaha]

Update to kind-1.27. I have verified that e2e test on Arm64 works well in kind-1.27 cluster.

[brianmcarey]

For adding a provider - its generally better to copy the existing provider in the first commit and then make the required updates. It can be difficult to update a provider like this as there maybe lanes in kubevirt that still rely on kind-1.23 but the update PR will fail because the provider no longer exists.

The old provider can be removed easily in a follow up PR.

[zhlhahaha]

For adding a provider - its generally better to copy the existing provider in the first commit and then make the required updates. It can be difficult to update a provider like this as there maybe lanes in kubevirt that still rely on kind-1.23 but the update PR will fail because the provider no longer exists.

The old provider can be removed easily in a follow up PR.

Yes, you are right. Updated.

[kubevirt-bot]

@zhlhahaha: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
check-up-kind-1.25-vgpu	a813f5d	link	false	/test check-up-kind-1.25-vgpu

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. I understand the commands that are listed here.

[oshoval]

Thanks

[oshoval]

Can you please remove the previous folder ?
kind-1.23 (unless I missed that it was removed or so)
unless you want to do it on a different PR
note that we doing it on steps because we have to bump in kubevirt,
but imho if it doesn't posses risks for you you can do it in one shot

[zhlhahaha]

Can you please remove the previous folder ? kind-1.23 (unless I missed that it was removed or so) unless you want to do it on a different PR note that we doing it on steps because we have to bump in kubevirt,

Yes, we will remove kind-1.23 in follow up PR. as you can see @brianmcarey 's comments #1027 (review)

but imho if it doesn't posses risks for you you can do it in one shot

I have a little concern that if we remove kind-1.23 in this PR, there would be some time gap among sync kubevirtci, kubevirt, and updating the arm64 e2e test job in project-infra. The time gap may lead to crash of e2e test on Arm64. By keeping the kind-1.23, we can make sure the migration of e2e test on Arm64 smoothly from kind-1.23 to kind-1.27.

[oshoval]

Thanks

[oshoval]

Weird it didn't catch the approval

/lgtm

[brianmcarey]

/approve

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: brianmcarey

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:

• OWNERS [brianmcarey]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment