Merge pull request #761 from benyanke/patch-1

Allowing TTL to be specified by Env var
This commit is contained in:
Raúl Sánchez 2018-04-05 18:51:52 +02:00 committed by GitHub
commit 4e255f2825
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 9 additions and 2 deletions

View File

@ -11,7 +11,7 @@ Rancher External DNS service powered by DigitalOcean
#### Usage
##### DigitalOcean DNS record TTL
The DigitalOcean API currently does not support per-record TTL setting. You should configure the global TTL setting for the domain manually and set it to a low value (e.g. 60).
The DigitalOcean API currently supports per-record TTL setting (https://developers.digitalocean.com/documentation/v2/#create-a-new-domain-record), but it is not yet implemented in this tool. You should configure the global TTL setting for the domain manually and set it to a low value (e.g. 60).
##### Limitation when running the service on multiple Rancher servers

View File

@ -7,7 +7,7 @@ digitalocean:
DO_PAT: ${DO_PAT}
ROOT_DOMAIN: ${ROOT_DOMAIN}
NAME_TEMPLATE: ${NAME_TEMPLATE}
TTL: 300
TTL: ${DNS_TTL}
labels:
io.rancher.container.create_agent: "true"
io.rancher.container.agent.role: "external-dns"

View File

@ -15,6 +15,13 @@
description: "The domain name managed by DigitalOcean."
type: "string"
required: true
- variable: "DNS_TTL"
label: "TTL"
description: |
TTL used for new DNS records.
type: "string"
default: "300"
required: true
- variable: "NAME_TEMPLATE"
label: "DNS Name Template"
description: |