mirrors/external-dns
1
0
Fork 0
mirror of https://github.com/kubernetes-sigs/external-dns.git synced 2025-08-06 09:36:58 +02:00
Code Issues Packages Projects Releases Wiki Activity
f58f53a3e4
external-dns/docs/ttl.md
leigh schrandt 65f4239d44 provider=google: Add Ttl from annotations: 
Use `int64(ep.RecordTTL)` in `newRecord()`
Fallback to hardcoded 300s for backwards-compat
Add `TestNewRecords()`
Add notes in *ttl.md*
2017-11-14 15:23:51 -07:00

1.3 KiB
Raw Blame History

Configure DNS record TTL (Time-To-Live)

An optional annotation external-dns.alpha.kubernetes.io/ttl is available to customize the TTL value of a DNS record.

To configure it, simply annotate a service/ingress, e.g.:

apiVersion: v1
kind: Service
metadata:
  annotations:
    external-dns.alpha.kubernetes.io/hostname: nginx.external-dns-test.my-org.com.
    external-dns.alpha.kubernetes.io/ttl: "60"
  ...

TTL must be a positive integer encoded as string.

Providers

  • AWS (Route53)
  • Azure
  • Cloudflare
  • DigitalOcean
  • Google
  • InMemory

PRs welcome!

Notes

When the external-dns.alpha.kubernetes.io/ttl annotation is not provided, the Ttl will default to 0 seconds and enpoint.TTL.isConfigured() will be false.

AWS Provider

The AWS Provider overrides the value to 300s when the Ttl is 0. This value is a constant in the provider code.

Google Provider

Previously with the Google Provider, Ttl's were hard-coded to 300s. For safety, the Google Provider overrides the value to 300s when the Ttl is 0. This value is a constant in the provider code.

For the moment, it is impossible to use a Ttl value of 0 with the AWS and Google Providers. This behavior may change in the future.