Our actual CICO workspace pod, deployed on demand on our openshift CI cluster, is still using outdated CentOS Stream 8 images, themselves based on UBI8 from openshift images.
There were requests about upstream openshift moving to UBI9 and it seems there is finally momentum : https://github.com/openshift/jenkins/pull/1857
To be tracked and then updating our https://github.com/centosci/images/tree/master/cico-workspace images (built and distribued on quay.io)
Metadata Update from @arrfab: - Issue tagged with: centos-build-pipeline, centos-ci-infra, high-gain, medium-trouble
Metadata Update from @arrfab: - Issue priority set to: Waiting on External (was: Needs Review) - Issue tagged with: blocked
Revisiting as pull request upstream was merged and so normally available for openshift 4.16 and 4.17 but still blocked somehow. So follow this upstream ticket instead : https://github.com/openshift/jenkins/issues/1766
We had to recently just rebase our stream8 based container to almalinux8 just because there is still no ubi9 based jenkins container available on quay.io (see above ticket). Reason why we had to quickly convert our existing container was due to java 11 to java 17 bump requirement at the jenkins server container level (see https://pagure.io/centos-infra/issue/1607)
This is quite problematic and embarrassing that openshift team doesn't provide any kind of answer about why they updated jenkins server image/container but that agent itself is now unmaintained ...
Metadata Update from @arrfab: - Issue untagged with: medium-trouble - Issue tagged with: high-trouble
Metadata Update from @arrfab: - Issue assigned to arrfab
Log in to comment on this ticket.