We are still on branch 4.15.x for now on our various openshift clusters, but based on https://access.redhat.com/support/policy/updates/openshift , "full support" ended in September already and we're just getting some minimal fixes until August this year. Switching to 4.18.x branch (which itself is a LTS one) should be our main target at this point, but we'd have to :
Metadata Update from @arrfab: - Issue tagged with: centos-ci-infra, centos-common-infra, centos-stream, high-gain, high-trouble, investigation
If I understand https://access.redhat.com/support/policy/updates/openshift correctly, "full support" as already ended for the 4.16 release. Any chance you could bump all the way to 4.18?
@mhuin yeah, something to indeed consider but that would mean testing the full path through intermediate releases .. Trying to see when we can test that on our .stg. cluster and then just reproduce on our main one (and scheduled all the upgrades on same day, so multiple downtimes but in serial mode)
Metadata Update from @arrfab: - Issue assigned to arrfab
Validing first on our .stg. ocp cluster and there are breaking changes from 4.16 to 4.17 that need to be taken care of. (like migration from OpenshiftSDN to OVNKubernetes
Our .stg. cluster was already migrated from 4.15 to 4.16.x and is now being migrated to 4.17.x (after the reconfig needed for ovnkubernetes) More info after final upgrade and validation. If that all works, I'll just announce the same operation to ci-users list and schedule it (probably for next week)
stg cluster was updated to 4.18.9 :
oc version Client Version: 4.18.9 Kustomize Version: v5.4.2 Server Version: 4.18.9 Kubernetes Version: v1.31.7
So I'll just announce this to ci-users list (as all pods will be restarted mutliple times due to all serial upgrades)
Announced and scheduled for April 28th (Monday) : https://lists.centos.org/hyperkitty/list/ci-users@lists.centos.org/thread/E5IZJMTUQYQWI2HPLR5TT6WWISRPHBNW/
All updated/upgraded, so closing
Metadata Update from @arrfab: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.