ci(e2e): bump KubeVirt to v1.9.0-alpha.0 for k8s 1.36 compatibility

KubeVirt v1.8.2 publishes VMI status checksum fields (uint32 in Go) as
format: int32 in its generated CRD schema. k8s 1.36 enables strict
numeric format validation in CRDs via
https://github.com/kubernetes/kubernetes/pull/136582, which now rejects
the legacy schema and causes virt-handler to enter an infinite VMI
status update re-enqueue loop. Live migrations never complete and the
descheduler e2e TestLiveMigrationInBackground times out.

The schema fix landed upstream in
https://github.com/kubevirt/kubevirt/pull/17469 (merged to main on
2026-04-18, included in v1.9.0-alpha.0 tagged 2026-05-11) but was not
backported to release-1.8, so no v1.8.x release contains it. Bump the
default KUBEVIRT_VERSION to v1.9.0-alpha.0 so the e2e suite consumes a
release whose generated CRDs are compatible with k8s 1.36's stricter
validator.

Tracked in https://github.com/kubevirt/kubevirt/issues/17858.
This commit is contained in:
Amir Alavi
2026-05-19 15:06:11 -04:00
parent 2119baee3d
commit 745146e411

View File

@@ -27,7 +27,13 @@ KIND_VERSION=${KIND_VERSION:-v0.31.0}
SKIP_KUBECTL_INSTALL=${SKIP_KUBECTL_INSTALL:-}
SKIP_KIND_INSTALL=${SKIP_KIND_INSTALL:-}
SKIP_KUBEVIRT_INSTALL=${SKIP_KUBEVIRT_INSTALL:-}
KUBEVIRT_VERSION=${KUBEVIRT_VERSION:-v1.8.2}
# v1.9.0-alpha.0 (or newer) is required for Kubernetes v1.36+, which
# enforces stricter CRD numeric format validation
# (https://github.com/kubernetes/kubernetes/pull/136582) and rejects the
# pre-fix VMI checksum status schema present in v1.8.x. Fixed upstream
# by https://github.com/kubevirt/kubevirt/pull/17469 (not backported to
# v1.8.x). See https://github.com/kubevirt/kubevirt/issues/17858.
KUBEVIRT_VERSION=${KUBEVIRT_VERSION:-v1.9.0-alpha.0}
# Build a descheduler image
IMAGE_TAG=v$(date +%Y%m%d)-$(git describe --tags)