1. Proposed title of this feature request

Support for DNSEndpoint CustomResourceDefinition (CRD) in Red Hat ExternalDNS Operator to enable direct management of DNS records with multiple targets

       2. What is the nature and description of the request?

The Red Hat ExternalDNS Operator currently does not include or support the DNSEndpoint CustomResourceDefinition (CRD), which is part of the upstream ExternalDNS project. This CRD enables a declarative approach for managing DNS records directly using Kubernetes-native custom resources.

This feature request is to enhance the Red Hat ExternalDNS Operator by including support for the DNSEndpoint CRD, similar to what is provided in the upstream Helm chart installation of ExternalDNS. This would allow users to define DNS records—including records with multiple targets—by creating instances of the DNSEndpoint kind.

Reference (Upstream):

• https://kubernetes-sigs.github.io/external-dns/latest/docs/sources/crd/#using-crd-source-to-manage-dns-records-in-different-dns-providers

• https://artifacthub.io/packages/helm/external-dns/external-dns

3. Why does the customer need this? (List the business requirements here)

Example use case required by customer:

apiVersion: externaldns.k8s.io/v1alpha1
kind: DNSEndpoint
metadata:
  name: my-test-prod
spec:
  endpoints:
    - dnsName: "*.my-test-prod.my-domain.com"
      recordTTL: 300
      recordType: A
      targets:
        - "10.1.x.x"
        - "10.2.x.x" 

4. List any affected packages or components.

Red Hat ExternalDNS Operator