Use k8s 1.35 for special network lanes

[orelmisan]

What this PR does / why we need it:
Update the special presubmit and periodic network jobs to use k8s v1.35.

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:

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:

NONE

[dosubot]

Related Documentation

No published documentation to review for changes on this repository.

Write your first living document

^{How did I do? Any feedback?}  

[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 assign vladikr for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• 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

[orelmisan]

/cc @nirdothan @frenzyfriday

[sourcery-ai]

Hey - I've left some high level feedback:

• Consider centralizing the k8s version used by these network lanes (e.g., via a shared variable or anchor) so that future version bumps don’t require manual string updates in multiple job names and TARGET values.
• Double-check whether there are any related references (e.g., dashboards, job filters, or alerts) that still point to the old k8s-1.34-*-sig-network job names so they remain aligned with the new 1.35 lanes.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Consider centralizing the k8s version used by these network lanes (e.g., via a shared variable or anchor) so that future version bumps don’t require manual string updates in multiple job names and TARGET values.
- Double-check whether there are any related references (e.g., dashboards, job filters, or alerts) that still point to the old `k8s-1.34-*-sig-network` job names so they remain aligned with the new 1.35 lanes.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[frenzyfriday]

lgtm, thanks!

[nirdothan]

Seems that regular 4.35 network lanes are already pretty stable. Thank you!

[kubevirt-bot]

Pull requests that are marked with lgtm should receive a review
from an approver within 1 week.

After that period the bot marks them with the label needs-approver-review.

/label needs-approver-review