kubevirt,vgpu: Bump vgpu lanes to use new kind-1.30-vgpu provider

[brianmcarey]

What this PR does / why we need it:

The vgpu lanes are currently testing against kubernetes v1.27 which is no longer supported on the main branch of kubevirt.

Update these lanes to use the new provider kind-1.30-vgpu.

This requires the following PR to be merged into kubevirt first: https://github.com/kubevirt/kubevirt/pull/12244

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 #

Special notes for your reviewer:

/cc @dhiller @xpivarc

Checklist

This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR. Approvers are expected to review this list.

• [ ] Design: A design document was considered and is present (link) or not required
• [ ] PR: The PR description is expressive enough and will help future contributors
• [ ] Code: Write code that humans can understand and Keep it simple
• [ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
• [ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
• [ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
• [ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
• [ ] Community: Announcement to kubevirt-dev was considered

Release note:

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Once this PR has been reviewed and has the lgtm label, please ask for approval from brianmcarey. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files: - **[github/ci/prow-deploy/files/jobs/kubevirt/kubevirt/OWNERS](https://github.com/kubevirt/project-infra/blob/main/github/ci/prow-deploy/files/jobs/kubevirt/kubevirt/OWNERS)** Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

[brianmcarey]

/hold

as mentioned in the description - this requires https://github.com/kubevirt/kubevirt/pull/12244 to be merged.

[brianmcarey]

/rehearse

[kubevirt-bot]

Rehearsal jobs created for this PR:

rehearsal-pull-kubevirt-e2e-kind-1.30-vgpu

You can trigger rehearsal for all jobs by commenting either /rehearse or /rehearse all on this PR.

For a specific PR you can comment /rehearse {job-name}.

For a list of jobs that you can rehearse you can comment /rehearse ?.

[brianmcarey]

/rehearse

[kubevirt-bot]

Rehearsal jobs created for this PR:

rehearsal-pull-kubevirt-e2e-kind-1.30-vgpu

You can trigger rehearsal for all jobs by commenting either /rehearse or /rehearse all on this PR.

For a specific PR you can comment /rehearse {job-name}.

For a list of jobs that you can rehearse you can comment /rehearse ?.

[brianmcarey]

/rehearse

[kubevirt-bot]

Rehearsal jobs created for this PR:

rehearsal-pull-kubevirt-e2e-kind-1.30-vgpu

You can trigger rehearsal for all jobs by commenting either /rehearse or /rehearse all on this PR.

For a specific PR you can comment /rehearse {job-name}.

For a list of jobs that you can rehearse you can comment /rehearse ?.

[brianmcarey]

/rehearse

[kubevirt-bot]

Rehearsal jobs created for this PR:

rehearsal-pull-kubevirt-e2e-kind-1.30-vgpu

You can trigger rehearsal for all jobs by commenting either /rehearse or /rehearse all on this PR.

For a specific PR you can comment /rehearse {job-name}.

For a list of jobs that you can rehearse you can comment /rehearse ?.

[dhiller]

@brianmcarey so I figure due to the still flaky history around the lane we are not there yet?

[brianmcarey]

/rehearse

[kubevirt-bot]

Rehearsal jobs created for this PR:

rehearsal-pull-kubevirt-e2e-kind-1.30-vgpu

You can trigger rehearsal for all jobs by commenting either /rehearse or /rehearse all on this PR.

For a specific PR you can comment /rehearse {job-name}.

For a list of jobs that you can rehearse you can comment /rehearse ?.

[brianmcarey]

/rehearse

[kubevirt-bot]

Rehearsal jobs created for this PR:

rehearsal-pull-kubevirt-e2e-kind-1.30-vgpu

You can trigger rehearsal for all jobs by commenting either /rehearse or /rehearse all on this PR.

For a specific PR you can comment /rehearse {job-name}.

For a list of jobs that you can rehearse you can comment /rehearse ?.

[xpivarc]

@brianmcarey is this ready?

[brianmcarey]

@brianmcarey is this ready?

No still seeing intermittent failures on cluster-up. I haven't had a chance to come back to this yet.

[brianmcarey]

/rehearse

[kubevirt-bot]

Rehearsal jobs created for this PR:

rehearsal-pull-kubevirt-e2e-kind-1.30-vgpu

You can trigger rehearsal for all jobs by commenting either /rehearse or /rehearse all on this PR.

For a specific PR you can comment /rehearse {job-name}.

For a list of jobs that you can rehearse you can comment /rehearse ?.

[kubevirt-bot]

PR needs rebase.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.