Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-7197

[External DNS Operator] CRD source has not been implemented yet

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Network - IngressDNS
    • None
    • None
    • Product / Portfolio Work
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Proposed title of this feature request

       The ability to use CRD source

      What is the nature and description of the request?

       My customer has asked if we can consider something like this is (see attached image) what I was expecting to do external-dns/docs/sources/crd/dnsendpoint-example.yaml at master · kubernetes-sigs/external-dns · GitHub

      For example:

      apiVersion: externaldns.k8s.io/v1alpha1
      kind: DNSEndpoint
      metadata:
        name: examplednsrecord
      spec:
        endpoints:
        - dnsName: foo.bar.com
          recordTTL: 180
          recordType: A
          targets:
          - 192.168.99.216
          # Provider specific configurations are set like an annotation would on other sources
          providerSpecific:
            - name: external-dns.alpha.kubernetes.io/cloudflare-proxied
              value: "true"

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

      They wish to be able to use the CRD's for configuring this operator
      4. List any affected packages or components.

              mschmitt-redhat Mark Schmitt
              rhn-support-andbartl Andy Bartlett
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                None
                None