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/installer/openshift-installer-master.yaml
  e2e-metal-ipi-sdn
  e2e-metal-ipi-sdn-swapped-hosts
  e2e-openstack-sdn-parallel
  e2e-nutanix-sdn

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:

• The installer should probably keep at least one SDN-based job until 4.17, to ensure that it doesn't somehow manage to completely break SDN installs while CI still depends on them working in other places. But 4 jobs is probably too many for something that it allegedly doesn't even support
• installer uses the common pattern of testing baremetal with sdn+ipv4 (e2e-metal-ipi-sdn) 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.
• e2e-metal-ipi-sdn-swapped-hosts looks like it is testing something to do with dev-scripts, not something to do with openshift-sdn, and should probably just be migrated to ovn-kubernetes immediately.
• e2e-openstack-sdn-parallel is very "matrixy", combining a weird platform, a weird network plugin, and a specific TEST_SUITE. I'm not sure if it is redundant or not.
• e2e-nutanix-sdn is probably already entirely redundant with e2e-nutanix-ovn and could be removed.