Please be advised that the CentOS CI Production Openshift cluster is due for scheduled maintenance from 06:00 to 08:00 UTC on 2025-04-28 . During this period necessary updates will be applied to the cluster.
The upgrade is not expected to be service affecting, however there might be periods of slight performance degradation (pods restarting on other workers) during this maintenance period. We apologize for any inconvenience that this may cause.
Detailed version : (see https://pagure.io/centos-infra/issue/1609) We're still running 4.15.x openshift, and we're due to some upgrades in a row to jump to 4.18.x These updates will require some time and so will restart all your pods multiple times. The longest operation is the conversion to OVN-kubernetest config type (instead of deprecated/removed now OpenShiftSDN one)
We tested all the intermediate steps on our staging cluster and all pods were coming back, so we're confident that it should still work for you after the upgrade, but at least you're aware of what's coming and why some of your CI jobs would be stopped/restarted by jenkins (if you use jenkins that is)
On 24/04/2025 15:29, Fabian Arrotin wrote:
Please be advised that the CentOS CI Production Openshift cluster is due for scheduled maintenance from 06:00 to 08:00 UTC on 2025-04-28 . During this period necessary updates will be applied to the cluster.
The upgrade is not expected to be service affecting, however there might be periods of slight performance degradation (pods restarting on other workers) during this maintenance period. We apologize for any inconvenience that this may cause.
Detailed version : (see https://pagure.io/centos-infra/issue/1609) We're still running 4.15.x openshift, and we're due to some upgrades in a row to jump to 4.18.x These updates will require some time and so will restart all your pods multiple times. The longest operation is the conversion to OVN-kubernetest config type (instead of deprecated/removed now OpenShiftSDN one)
We tested all the intermediate steps on our staging cluster and all pods were coming back, so we're confident that it should still work for you after the upgrade, but at least you're aware of what's coming and why some of your CI jobs would be stopped/restarted by jenkins (if you use jenkins that is)
While the date is correct, the 2hours slot isn't .. it will start around the communicated hour but due to number of pods to reschedule/move during all the upgrades, we consider that the whole operation should take ~6hours .. we'll just announce when it will be all done
Thanks for your comprehending,
-
Fabian Arrotin