Traefik & Etcd

A Story of KV store & Containers

Store your configuration in etcd and let Traefik do the rest!

Routing Configuration

See the dedicated section in routing.

Provider Configuration

endpoints

Required, Default=”127.0.0.1:2379”

Defines how to access etcd.

File (YAML)

providers:
  etcd:
    endpoints:
      - "127.0.0.1:2379"

File (TOML)

[providers.etcd]
  endpoints = ["127.0.0.1:2379"]

CLI

--providers.etcd.endpoints=127.0.0.1:2379

rootKey

Required, Default=”traefik”

Defines the root key of the configuration.

File (YAML)

providers:
  etcd:
    rootKey: "traefik"

File (TOML)

[providers.etcd]
  rootKey = "traefik"

CLI

--providers.etcd.rootkey=traefik

username

Optional, Default=””

Defines a username with which to connect to etcd.

File (YAML)

providers:
  etcd:
    # ...
    username: "foo"

File (TOML)

[providers.etcd]
  # ...
  username = "foo"

CLI

--providers.etcd.username=foo

password

Optional, Default=””

Defines a password with which to connect to etcd.

File (YAML)

providers:
  etcd:
    # ...
    password: "bar"

File (TOML)

[providers.etcd]
  # ...
  password = "bar"

CLI

--providers.etcd.password=foo

tls

Optional

Defines the TLS configuration used for the secure connection to etcd.

ca

Optional

ca is the path to the certificate authority used for the secure connection to etcd, it defaults to the system bundle.

File (YAML)

providers:
  etcd:
    tls:
      ca: path/to/ca.crt

File (TOML)

[providers.etcd.tls]
  ca = "path/to/ca.crt"

CLI

--providers.etcd.tls.ca=path/to/ca.crt

caOptional

Optional

The value of caOptional defines which policy should be used for the secure connection with TLS Client Authentication to etcd.

If ca is undefined, this option will be ignored, and no client certificate will be requested during the handshake. Any provided certificate will thus never be verified.

When this option is set to true, a client certificate is requested during the handshake but is not required. If a certificate is sent, it is required to be valid.

When this option is set to false, a client certificate is requested during the handshake, and at least one valid certificate should be sent by the client.

File (YAML)

providers:
  etcd:
    tls:
      caOptional: true

File (TOML)

[providers.etcd.tls]
  caOptional = true

CLI

--providers.etcd.tls.caOptional=true

cert

Optional

cert is the path to the public certificate used for the secure connection to etcd. When using this option, setting the key option is required.

File (YAML)

providers:
  etcd:
    tls:
      cert: path/to/foo.cert
      key: path/to/foo.key

File (TOML)

[providers.etcd.tls]
  cert = "path/to/foo.cert"
  key = "path/to/foo.key"

CLI

--providers.etcd.tls.cert=path/to/foo.cert
--providers.etcd.tls.key=path/to/foo.key

key

Optional

key is the path to the private key used for the secure connection to etcd. When using this option, setting the cert option is required.

File (YAML)

providers:
  etcd:
    tls:
      cert: path/to/foo.cert
      key: path/to/foo.key

File (TOML)

[providers.etcd.tls]
  cert = "path/to/foo.cert"
  key = "path/to/foo.key"

CLI

--providers.etcd.tls.cert=path/to/foo.cert
--providers.etcd.tls.key=path/to/foo.key

insecureSkipVerify

Optional, Default=false

If insecureSkipVerify is true, the TLS connection to etcd accepts any certificate presented by the server regardless of the hostnames it covers.

File (YAML)

providers:
  etcd:
    tls:
      insecureSkipVerify: true

File (TOML)

[providers.etcd.tls]
  insecureSkipVerify = true

CLI

--providers.etcd.tls.insecureSkipVerify=true