57 lines
2.3 KiB
Markdown
57 lines
2.3 KiB
Markdown
## Infoblox DNS
|
|
|
|
Rancher External DNS service powered by Infoblox DNS
|
|
|
|
#### Usage
|
|
|
|
##### Infloblox Password
|
|
|
|
Infoblox password could be provided in 2 ways, depending what you set at `Infoblox password type` enum:
|
|
|
|
- `env` by environment var.
|
|
|
|
Infoblox password is provided at `Infoblox password | secret name` field. This generates an enviroment variable inside container, `INFOBLOX_PASSWORD`, that contains the password in CLEAR.
|
|
|
|
- `secret` by rancher secret.
|
|
|
|
Infoblox password is provided by a Rancher Secret to secure it. Secret name is provided at `Infoblox password | secret name` field.
|
|
|
|
Previous steps are required to use rancher secrets:
|
|
1. Deploy Rancher Secrets service from library catalog, before deploying this stack.
|
|
2. Create a rancher secret with your infoblox password. From ui, `Infrastructure -> Secrets`.
|
|
3. Deploy this stack, setting `Infoblox password type` enum to `secret` and setting `Infoblox password | secret name` field to previously created secret name.
|
|
|
|
##### Supported host labels
|
|
|
|
`io.rancher.host.external_dns_ip`
|
|
Override the IP address used in DNS records for containers running on the host. Defaults to the IP address the host is registered with in Rancher.
|
|
|
|
`io.rancher.host.external_dns`
|
|
Accepts 'true' (default) or 'false'
|
|
When this is set to 'false' no DNS records will ever be created for containers running on this host.
|
|
|
|
##### Supported service labels
|
|
|
|
`io.rancher.service.external_dns`
|
|
Accepts 'always', 'never' or 'auto' (default)
|
|
- `always`: Always create DNS records for this service
|
|
- `never`: Never create DNS records for this service
|
|
- `auto`: Create DNS records for this service if it exposes ports on the host
|
|
|
|
`io.rancher.service.external_dns_name_template`
|
|
Custom DNS name template that overrides global custom DNS name template (see below) of default DNS name template for a specific service
|
|
|
|
##### Custom DNS name template
|
|
|
|
By default DNS entries are named `<service>.<stack>.<environment>.<domain>`.
|
|
You can specify a custom name template used to construct the subdomain part (left of the domain/zone name) of the DNS records. The following placeholders are supported:
|
|
|
|
* `%{{service_name}}`
|
|
* `%{{stack_name}}`
|
|
* `%{{environment_name}}`
|
|
|
|
**Example:**
|
|
|
|
`%{{stack_name}}-%{{service_name}}.statictext`
|
|
|
|
Make sure to only use characters in static text and separators that your provider allows in DNS names. |