How to create SRV record instead of the default TXT record using external-dns

[manan00]

We have an application that does SRV lookup to connect to the ILB of the container.
I have added the following annotations to create a DNS record in my service.yaml file

annotations:
external-dns.alpha.kubernetes.io/hostname
external-dns.alpha.kubernetes.io/ttl

This creates TXT and A record. Is there any way to get SRV record created instead of TXT record?
I can see external-dns do support SRV record as per below:
https://github.com/kubernetes-sigs/external-dns/blob/master/provider/recordfilter.go

Please advise.

[wolmi]

In my case, I'm managing a set of devices that needs to be discovered by Prometheus using SRV.
I'm using CRD to create some A records for each organization that includes a group of devices, and now I need a way to create an SRV record that points to the new records created. Next is my CRDs:

apiVersion: externaldns.k8s.io/v1alpha1
kind: DNSEndpoint
metadata:
 name: a-record
 namespace: external-dns
spec:
 endpoints:
 - dnsName: a.domain.internal
   recordType: A
   targets:
     - 192.168.22.1
     - 192.168.22.2

apiVersion: externaldns.k8s.io/v1alpha1
kind: DNSEndpoint
metadata:
 name: b-record
 namespace: external-dns
spec:
 endpoints:
 - dnsName: b.domain.internal
   recordType: A
   targets:
     - 192.168.23.1
     - 192.168.23.2

apiVersion: externaldns.k8s.io/v1alpha1
kind: DNSEndpoint
metadata:
 name: srv-record
 namespace: external-dns
spec:
 endpoints:
 - dnsName: _srv._tcp.domain.internal
   recordType: SRV
   targets:
     - "0 0 8999 a.domain.internal"
     - "0 0 8999 b.domain.internal"

The A records are created properly but the SRV is not created and no logs or any message appears indicating why is not creating the record.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[chris-schra]

/remove-lifecycle stale

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[aschaber1]

/reopen

[k8s-ci-robot]

@aschaber1: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.