openshift-sdn is no longer supported for new installs as of 4.15, and it will be completely removed from OpenShift in 4.17.

Your component currently has one or more CI jobs that use openshift-sdn:

ci-operator/config/openshift/cluster-baremetal-operator/openshift-cluster-baremetal-operator-master.yaml
  e2e-metal-ipi-sdn-bm
  e2e-metal-ipi-sdn-serial-ipv4
  e2e-metal-ipi-sdn-upgrade

These jobs will need to be removed or migrated to ovn-kubernetes by OCP 4.17. In some cases, if you were not intentionally testing openshift-sdn, it may make sense to start migrating these jobs in 4.15. You may want to split this bug into multiple bugs for different OCP versions.

Component-specific notes:

• cluster-baremetal-operator uses the common pattern of testing baremetal with sdn+ipv4 (e2e-metal-ipi-sdn-bm) and ovn+ipv6 (e2e-metal-ipi-ovn-ipv6). Depending on your testing needs, it may make sense to remove the sdn+ipv4 job and keep just the ovn+ipv6 one, or to replace the sdn+ipv4 job with ovn+ipv4, or to replace both jobs with a single ovn+ipv4 job.
• It follows the same pattern with upgrade tests, doing sdn+ipv4 (e2e-metal-ipi-sdn-upgrade) and ovn+ipv6 (e2e-metal-ipi-upgrade-ovn-ipv6). Similar considerations apply.
• e2e-metal-ipi-sdn-serial-ipv4 is the only serial job and presumably did not intend to be testing against sdn, and thus should probably be rebased onto the (new) baremetalds-e2e-serial-ovn-ipv4 workflow.
• Note that the e2e-metal-sdn-assisted job is not actually SDN-based and you should merge https://github.com/openshift/release/pull/46344 to rename it.