KubeVirt CI Prow Control Plane Cluster Maintenance Window - 20th Feb. 12pm -> 21th Feb. 12pm (UTC)

[Denis Ollier Pinas]

Hi KubeVirt contributors,

The OpenShift version of the KubeVirt CI Prow Control Plane cluster is reaching its end of life in August and needs to be updated.

For this purpose, a maintenance window is scheduled to start this Friday (20th Feb.) early in the afternoon (EMEA timezone) and to finish during the week-end.

The update will be quite long since it will go through several steps before catching up the latest LTS version:

    OCP-4.16 -> OCP-v4.17 -> RHEL-9 workers -> OCP-v4.18 -> RHCOS workers -> OCP-v4.19 -> OCP-v4.20

The Prow Control Plane cluster will still be available during the update but it will experience a few hiccups.
It is expected for some ProwJobs to fail when the nodes will be evicted to be replaced by updated workers.
You might need to use `/retest` more than usual.

Unless something unexpected happens this maintenance should be quite smooth overall.

Several rehearsals were performed to reduce the risk of unforeseen events.

Don't hesitate to reach us if you have any concerns.

Regards,

The KubeVirt CI maintenance team.

[Orel Misan]

Hi Denis,

The v1.8 feature freeze is scheduled for February 25th [1]. Given that there are still many VEPs that need to be merged, is it possible to postpone the maintenance until after this date?

Thanks,

Orel

[1] https://github.com/kubevirt/sig-release/blob/259100fd99bef0e15918f4dde3a0e89fb8516b39/releases/v1.8/schedule.md?plain=1#L15

--
You received this message because you are subscribed to the Google Groups "kubevirt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubevirt-dev...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/kubevirt-dev/ad84b0e5-6bb0-4cf7-9387-7ce9743b6e78n%40googlegroups.com.

[doll...@redhat.com]

Le lundi 16 février 2026 à 09:20 +0200, Orel Misan a écrit :

Hi Denis,

The v1.8 feature freeze is scheduled for February 25th [1]. Given that there are still many VEPs that need to be merged, is it possible to postpone the maintenance until after this date?

Thanks for bringing this up.

The maintenance will be postponed by one week, to February 27th.

It will be pushed back further if necessary in the event that the feature freeze deadline is extended.

[Orel Misan]

Thank you Denis!

[doll...@redhat.com]

Hi,

Given all the extension requests for 1.8 VEPs, the update is being postponed by (at least) one week and is now scheduled for March 6th.

Best Regards,