Skip to content

Update kubevirtci to latest version#175

Open
awels wants to merge 1 commit into
kubevirt:mainfrom
awels:update_kubevirtci
Open

Update kubevirtci to latest version#175
awels wants to merge 1 commit into
kubevirt:mainfrom
awels:update_kubevirtci

Conversation

@awels

@awels awels commented Feb 5, 2026

Copy link
Copy Markdown
Member

Also update the tenant cluster version to 1.33.7

NONE

@kubevirt-bot kubevirt-bot added release-note-none Denotes a PR that doesn't merit a release note. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. labels Feb 5, 2026
Comment thread kubevirtci Outdated
@@ -5,7 +5,7 @@ set -e
export KUBEVIRT_PROVIDER=${KUBEVIRT_PROVIDER:-k8s-1.30}
export CAPK_GUEST_K8S_VERSION=${CAPK_GUEST_K8S_VERSION:-v1.30.1}

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do you want to update this too?

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

and possibly NODE_VM_IMAGE_TEMPLATE

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point missed those.

Comment thread kubevirtci Outdated
@@ -5,7 +5,7 @@ set -e
export KUBEVIRT_PROVIDER=${KUBEVIRT_PROVIDER:-k8s-1.30}

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks like we also have to swap this, CI is red over it since 1.30 doesn't exist

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done let me push the fix.

@awels awels force-pushed the update_kubevirtci branch from 415f224 to fb5b53c Compare February 5, 2026 15:08
@awels awels force-pushed the update_kubevirtci branch from fb5b53c to 68a4832 Compare February 6, 2026 15:42
@kubevirt-bot kubevirt-bot added size/M and removed size/S labels Feb 6, 2026
@awels awels force-pushed the update_kubevirtci branch from 68a4832 to f83c75b Compare February 6, 2026 16:05
@awels awels force-pushed the update_kubevirtci branch 2 times, most recently from a32b484 to d84fe45 Compare April 3, 2026 14:38
Also update the tenant cluster version to 1.33.7

Signed-off-by: Alexander Wels <awels@redhat.com>
@awels awels force-pushed the update_kubevirtci branch from d84fe45 to d1c7a8b Compare April 3, 2026 15:02
@awels

awels commented Apr 3, 2026

Copy link
Copy Markdown
Member Author

/approve

@kubevirt-bot

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: awels

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

The pull request process is described here

Details Needs approval from an approver in each of these files:

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

@kubevirt-bot kubevirt-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 3, 2026
@kubevirt-bot

Copy link
Copy Markdown

There has been no activity on this PR for 45 days.
To protect limited CI resources, it has been automatically labelled 'stale'.
This PR will automatically rot after an additional 14 days of inactivity, and will be closed shortly after that.

What you can do:

  • If the PR is waiting on you to respond to a question or feedback and/or update the PR, please do so.
  • You can mark the PR as fresh and remove the label with the following command: /remove-lifecycle stale
  • If this PR is safe to close now, please help the project by closing it with: /close
  • If you need attention on this PR from a reviewer, you can raise it on the agenda of the relevant SIG meeting or KubeVirt Community meeting, or ping the kubevirt-dev slack channel.

/lifecycle stale

@kubevirt-bot kubevirt-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 18, 2026
@kubevirt-bot

Copy link
Copy Markdown

There has been no activity on this PR for 59 days and it has been stale for 14 days.
To protect limited CI resources, it has been automatically labelled 'rotten' and will be closed in 7 days.

What you can do:

  • If the PR is waiting on you to respond to a question or feedback and/or update the PR, please do so.
  • You can mark the PR as fresh and remove the label with the following command: /remove-lifecycle rotten
  • If this PR is safe to close now, please help the project by closing it with: /close
  • If you need attention on this PR from a reviewer, you can raise it on the agenda of the relevant SIG meeting or KubeVirt Community meeting, or ping the kubevirt-dev slack channel.

/lifecycle rotten

@kubevirt-bot kubevirt-bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jun 1, 2026
@kubevirt-bot

Copy link
Copy Markdown

There has been no activity on this PR for 66 days and it has been rotten for 7 days.
To protect limited CI resources, it has been automatically closed.

What you can do:

/close

@kubevirt-bot

Copy link
Copy Markdown

@kubevirt-bot: Closed this PR.

Details

In response to this:

There has been no activity on this PR for 66 days and it has been rotten for 7 days.
To protect limited CI resources, it has been automatically closed.

What you can do:

/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.

@awels awels reopened this Jun 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. release-note-none Denotes a PR that doesn't merit a release note. size/M

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants