Traefik & etcd¶
Configuration Example¶
You can enable the etcd provider as detailed below:
providers:
etcd: {}
[providers.etcd]
--providers.etcd=true
Configuration Options¶
Field | Description | Default | Required |
---|---|---|---|
providers.providersThrottleDuration |
Minimum amount of time to wait for, after a configuration reload, before taking into account any new configuration refresh event. If multiple events occur within this time, only the most recent one is taken into account, and all others are discarded. This option cannot be set per provider, but the throttling algorithm applies to each of them independently. |
2s | No |
providers.etcd.endpoints |
Defines the endpoint to access etcd. | "127.0.0.1:2379" | Yes |
providers.etcd.rootKey |
Defines the root key for the configuration. | "traefik" | Yes |
providers.etcd.username |
Defines a username with which to connect to etcd. | "" | No |
providers.etcd.password |
Defines a password for connecting to etcd. | "" | No |
providers.etcd.tls |
Defines the TLS configuration used for the secure connection to etcd. | - | No |
providers.etcd.tls.ca |
Defines the path to the certificate authority used for the secure connection to etcd, it defaults to the system bundle. | "" | No |
providers.etcd.tls.cert |
Defines the path to the public certificate used for the secure connection to etcd. When using this option, setting the key option is required. |
"" | Yes |
providers.etcd.tls.key |
Defines the path to the private key used for the secure connection to etcd. When using this option, setting the cert option is required. |
"" | Yes |
providers.etcd.tls.insecureSkipVerify |
Instructs the provider to accept any certificate presented by etcd when establishing a TLS connection, regardless of the hostnames the certificate covers. | false | No |
Routing Configuration¶
See the dedicated section in routing.