Update kind-1.27-vgpu cluster to latest kubernetes version

[brianmcarey]

The kind-1.27-vgpu cluster should be updated to a more recent version of Kubernetes as support for v1.27 is going to be dropped as part of the next KubeVirt release[1].

[1] https://github.com/kubevirt/sig-release/blob/main/releases/k8s-support-matrix.md

[brianmcarey]

/cc @xpivarc is there someone from sig-compute who would be interested in taking a look at this?

[kubevirt-bot]

@brianmcarey:
This request has been marked as suitable for new contributors.

Guidelines

• No Barrier to Entry
• Clear Task
• Solution Explained
• Provides Context
• Identifies Relevant Code
• Gives Examples
• Ready to Test
• Goldilocks priority
• Up-To-Date

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

/good-first-issue

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.

[kubevirt-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[anishbista60]

@brianmcarey can I work or it is specially for sigs ?

[brianmcarey]

@brianmcarey can I work or it is specially for sigs ?

We have an updated provider added here - #1210 - but it is having intermittent failures in CI so it hasn't been promoted to the kubevirt repo.
Failures with bringing up the cluster if you want to have a look into them - https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirtci/1228/check-up-kind-1.30-vgpu/1822556479895375872

[anishbista60]

@brianmcarey yeah sure i'll work and try to troubleshoot through logs .

[kubevirt-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

[kubevirt-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

[kubevirt-bot]

@kubevirt-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

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.