-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Open
Labels
area/provider/azureIssues or PRs related to azure providerIssues or PRs related to azure providerhelp wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.
Description
What would you like to be added:
Currently, at least for Azure, the TTL is hard coded to 300 seconds. It is possible to override this per endpoint but it would be very useful to set the default ttl on the external-dns service itself.
Why is this needed:
We want to use the concept of "convention over configuration" and since we need to lower the TTL we do not want to explicitly do so in all the ingresses we define, but rather define this centrally for our cluster. The hard coded value of 300 seconds means that clients sometimes cache invalid responses for up to 5 minutes, which is unacceptable in our situation.
gmelillo, wpjunior, pavlo-bondarenko, mikhailadvani, rodrigosouzazup and 9 more
Metadata
Metadata
Assignees
Labels
area/provider/azureIssues or PRs related to azure providerIssues or PRs related to azure providerhelp wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.