external-dns to use the fixed IP or dns-name for all records

[tarunm97]

can we put something like this, all the records that are created by the external DNS will use the same value for example in the deployment of the external DNS, e.g --fixed-dns-record-value=abcd.test.com and now every record which is created will use this as the DNS-record-value

like if I created ingress with nginx.abcd.com or prometheus.abcd.com all will route to the same record and then we will point the abcd.test.com

nginx.abcd.com ---> abcd.test.com [will automatically created by external-DNS, when kind: ingress is used] prometheus.abcd.com ---> abcd.test.com [will automatically created by external-DNS, when kind: ingress is used]

abcd.test.com ---> load-balancer-DNS-name [created-manually]

[aduzsardi]

Hello, i was also looking for this in the FAQ but wasn't there I would like to have a specific IP address used for all records , because it's forwarded from the router to the IP address of the service , the service will only have a private IP address at all times.

[aduzsardi]

never mind , i fixed it by using external-dns.alpha.kubernetes.io/target: annotation with an IP address

the only downside is that you have to add it on every resource , an alternative would be to have an argument/flag on the external-dns container

[cgroschupp]

You can use the --default-targets argument to set all records to a fixed set of records.

[aduzsardi]

thank you @cgroschupp , can you please post a link where all these arguments are documented ? i bet there are some other arguments that i don't know about that would be useful

[cgroschupp]

https://github.com/kubernetes-sigs/external-dns/blob/master/pkg/apis/externaldns/types.go#L443

Or you execute the binary/container with -h

[aduzsardi]

Wow , quite a lot of them. Thank you again!

[tarunmittal24]

@aduzsardi @cgroschupp , i have also used the external-dns.alpha.kubernetes.io/target: annotations, but same need to add in all, i have adding all my ingress to come to a specific domain name and then that to the load-balancer, same the one i have mentioned above when creating this issue.

[cgroschupp]

@tarunmittal24 please try --default-targets with the newest staging container image.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

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.