Issue #12763: Update communishift cluster to OVN from SDN networking - fedora-infrastructure

fedora-infrastructure

#12763 Update communishift cluster to OVN from SDN networking

Closed: Fixed with Explanation Sep 4, 2025 by kevin. Opened Sep 2, 2025 by kevin.

Our communishift cluster is stuck on 4.16.x currently because newer versions use OVN network and SDN has been dropped.

We should migrate it to OVN
( https://access.redhat.com/solutions/7057169 )
and then upgrade it to 4.17.x and then 4.18.x and then 4.19.x)

This has to be done before next month when 4.16.x drops out of support.

Openshift dedicated doesnt do this migration, they expect it to be self service.

kevin commented Sep 2, 2025

https://docs.redhat.com/en/documentation/red_hat_openshift_service_on_aws_classic_architecture/4/html/networking/ovn-kubernetes-network-plugin#migrate-from-openshift-sdn

seems to be the instructions for ROSA.

kevin commented Sep 2, 2025

Oh, we have OSD, not ROSA...

https://docs.redhat.com/en/documentation/openshift_dedicated/4/html/networking/ovn-kubernetes-network-plugin#migrate-sdn-ovn-ocm-cli_migrate-from-openshift-sdn-osd

Metadata Update from @smoliicek:
- Issue assigned to kevin
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: low-gain, medium-trouble

Sep 2, 2025

Metadata Update from @smoliicek:
- Issue untagged with: low-gain
- Issue tagged with: medium-gain

Sep 2, 2025

kevin commented Sep 3, 2025

I've upgraded the cluster to 4.16.46 (it needed to be newer than 4.16.43)

I've started the migration from sdn.

kevin commented Sep 3, 2025

Thats all done, but it's not showing the 4.17.x upgrade yet. Might need to take a while to refresh.

kevin commented Sep 4, 2025

I started the 4.17.x upgrade. Hopefully it will go smoothly.

kevin commented Sep 4, 2025

4.17.x went fine. Will move ahead once it shows 4.18.x.