External-dns: RFC2136 provider with TTL 0

[niriak]

Looks like the RFC2136 provider creates DNS records with TTL 0 (zero).
Is there any way to change that value?

Docker Image: docker.io/bitnami/external-dns:0.5.15-debian-9-r1

[adampl]

You can set a different TTL with an annotation, like this:
external-dns.alpha.kubernetes.io/ttl: "5"

[niriak]

Thanks, I'll try to be more specific: Is there a way to set a default TTL value that applies to all?

[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

[stefanlasiewski]

We need to wait for https://github.com/kubernetes-sigs/external-dns/pull/1412 to make it into a release

[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-testing, kubernetes/test-infra and/or fejta.
/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-testing, kubernetes/test-infra and/or fejta.
/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-testing, kubernetes/test-infra and/or fejta.
/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.