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-network-operator/openshift-cluster-network-operator-master.yaml
  e2e-gcp-sdn
  e2e-aws-sdn-upgrade
  e2e-aws-sdn-multi
  e2e-openstack-sdn
  e2e-aws-ovn-network-migration
  e2e-aws-sdn-network-migration-rollback
  e2e-aws-sdn-network-reverse-migration
  e2e-network-mtu-migration-sdn-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:

• Most of these jobs are definitely intentionally testing SDN and so should probably remain until 4.17. In particular, it is quite important that sdn-to-ovn migration work correctly in 4.15 and 4.16.
• e2e-openstack-sdn could perhaps be killed off without guilt, since e2e-openstack-ovn also exists.