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-etcd-operator/openshift-cluster-etcd-operator-master.yaml
  e2e-metal-ipi
  e2e-metal-ipi-serial-ipv4

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-etcd-operator uses the common pattern of testing baremetal with sdn+ipv4 (e2e-metal-ipi) 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-serial-ipv4 is ambiguous; there is another ovn-based serial job (e2e-aws-ovn-serial), so if cluster-etcd-operator doesn't care specifically about testing serial on baremetal, then e2e-metal-ipi-serial-ipv4 could just be deleted. Alternatively, if cluster-etcd-operator has a good reason for wanting deeper-than-average serial testing, e2e-metal-ipi-serial-ipv4 could be replaced with a job based on the baremetalds-e2e-serial-ovn-ipv6 workflow to provide baremetal+ipv6 serial testing in addition to the aws+ipv4 serial testing.