1. Proposed title of this feature request
Add support for consuming gateway API sources in OpenShift External DNS Operator

2. What is the nature and description of the request?
At the moment the External DNS Operator is limited to consuming Services, OpenShift Routes and custom CRDs. Customer would request this is enhanced to include the gateway API resources, in particular HTTPRoute and TLSRoute.

3. Why does the customer need this? (List the business requirements here)
Customers are looking to implement an alternative ingress into an OpenShift cluster and the existing sources do not fit the use case. As we understand it the Gateway API is the successor to the Ingress API. Without the support for these sources in the external-dns operator would require either using the upstream community supported version which we cannot do or build our own automation/operator to handle this which is a significant undertaking.

4. List any affected packages or components.

The external dns operator:
https://github.com/openshift/external-dns-operator/blob/main/api/v1beta1/externaldns_types.go#L472-L476

https://catalog.redhat.com/software/containers/edo/external-dns-rhel9-operator/66e18f40d57679c1bf6d0ac4?container-tabs=overview

5. What is the business impact that you are facing? How many customers are affected by this?

Customers are in a pilot phase of introducing a new platform. This will accelerate adoption of the platform and enable further testing.