kubevirt,presubmit: enable kubernetes v1.31 lanes to always run

[brianmcarey]

What this PR does / why we need it:

Kubernetes v1.31.0 has been released[1] and the k8s-1.31 periodic lanes look very stable[2]. Introduce the k8s-1.31 lanes to always run and required.

Move the kubernetes v1.29 test lanes to phase two and remove the kubernetes v1.28 test lanes.

Also update the compute-serial and compute-migrations lane to v1.31

[1] https://github.com/kubernetes/kubernetes/releases/tag/v1.31.0
[2] https://testgrid.kubernetes.io/kubevirt-periodics

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:

[brianmcarey]

/rehearse ?

[kubevirt-bot]

Rehearsal is available for the following jobs in this PR:

pull-kubevirt-e2e-k8s-1.31-sig-network
pull-kubevirt-e2e-k8s-1.31-sig-storage
pull-kubevirt-e2e-k8s-1.31-sig-compute-serial
pull-kubevirt-e2e-k8s-1.30-sig-network
pull-kubevirt-e2e-k8s-1.30-sig-compute
pull-kubevirt-e2e-k8s-1.31-sig-compute-migrations
pull-kubevirt-e2e-k8s-1.30-sig-storage
pull-kubevirt-e2e-k8s-1.31-sig-compute
pull-kubevirt-e2e-k8s-1.31-sig-operator
pull-kubevirt-e2e-k8s-1.30-sig-operator

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 pull-kubevirt-e2e-k8s-1.31-sig-compute-migrations
/rehearse pull-kubevirt-e2e-k8s-1.31-sig-compute-serial

[kubevirt-bot]

Rehearsal jobs created for this PR:

rehearsal-pull-kubevirt-e2e-k8s-1.31-sig-compute-serial
rehearsal-pull-kubevirt-e2e-k8s-1.31-sig-compute-migrations

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]

/approve

Thank you @brianmcarey - one question: did you use the tool to do that?

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dhiller

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:

• github/ci/prow-deploy/files/jobs/kubevirt/kubevirt/OWNERS [dhiller]

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

[brianmcarey]

/approve

Thank you @brianmcarey - one question: did you use the tool to do that?

I didn't use the tool as we still have the issue with the tool removing the run_before_merge: true due to the older test-infra dependency - #3478

[kubevirt-bot]

@brianmcarey: Updated the job-config configmap in namespace kubevirt-prow at cluster default using the following files:

• key kubevirt-periodics.yaml using file github/ci/prow-deploy/files/jobs/kubevirt/kubevirt/kubevirt-periodics.yaml
• key kubevirt-presubmits.yaml using file github/ci/prow-deploy/files/jobs/kubevirt/kubevirt/kubevirt-presubmits.yaml

In response to this:

What this PR does / why we need it:

Kubernetes v1.31.0 has been released[1] and the k8s-1.31 periodic lanes look very stable[2]. Introduce the k8s-1.31 lanes to always run and required.

Move the kubernetes v1.29 test lanes to phase two and remove the kubernetes v1.28 test lanes.

Also update the compute-serial and compute-migrations lane to v1.31

[1] https://github.com/kubernetes/kubernetes/releases/tag/v1.31.0
[2] https://testgrid.kubernetes.io/kubevirt-periodics

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:

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.