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/frr/openshift-frr-master.yaml
  metallb-e2e-metal-ipi

ci-operator/config/openshift/metallb/openshift-metallb-main.yaml
  metallb-e2e-metal-ipi

ci-operator/config/openshift/metallb-operator/openshift-metallb-operator-main.yaml
  metallb-e2e-metal-ipi

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 components that test bare metal have ended up with one sdn+ipv4 test and one ovn+ipv6 test. metallb and metallb-operator have instead ended up with sdn+ipv4 and ovn+ipv4. Depending on your testing needs, you could either just remove the sdn-based test, or else replace it with an ovn+ipv6 one.
• I'm guessing that "frr" goes with metallb since it has the same uncommon CI setup as metallb and metallb-operator? (Its OWNERS file claims that frr bugs should be filed under Networking / frr, but there is no such subcomponent.)