Boot Environment¶

Traefik Proxy’s configuration is divided into two main categories:

Install Configuration: (formerly known as the static configuration) Defines parameters that require Traefik to restart when changed. This includes entry points, providers, API/dashboard settings, and logging levels.
Routing Configuration: (formerly known as the dynamic configuration) Involves elements that can be updated without restarting Traefik, such as routers, services, and middlewares.

This section focuses on setting up the install configuration, which is essential for Traefik’s initial boot.

Configuration Methods¶

Traefik offers multiple methods to define install configuration.

Note

It’s crucial to choose one method and stick to it, as mixing different configuration options is not supported and can lead to unexpected behavior.

Here are the methods available for configuring the Traefik proxy:

File
CLI
Environment Variables
Helm

File¶

You can define the install configuration in a file using formats like YAML or TOML.

Configuration Example¶

traefik.yml (YAML)

entryPoints:
  web:
    address: ":80"
  websecure:
    address: ":443"

providers:
  docker: {}

api:
  dashboard: true

log:
  level: INFO

traefik.toml (TOML)

[entryPoints]
  [entryPoints.web]
    address = ":80"

  [entryPoints.websecure]
    address = ":443"

[providers]
  [providers.docker]

[api]
  dashboard = true

[log]
  level = "INFO"

Configuration File¶

At startup, Traefik searches for install configuration in a file named traefik.yml (or traefik.yaml or traefik.toml) in the following directories:

/etc/traefik/
$XDG_CONFIG_HOME/
$HOME/.config/
. (the current working directory).

You can override this behavior using the configFile argument like this:

traefik --configFile=foo/bar/myconfigfile.yml

CLI¶

Using the CLI, you can pass install configuration directly as command-line arguments when starting Traefik.

Configuration Example¶

CLI

traefik \
  --entryPoints.web.address=":80" \
  --entryPoints.websecure.address=":443" \
  --providers.docker \
  --api.dashboard \
  --log.level=INFO

Environment Variables¶

You can also set the install configuration using environment variables. Each option corresponds to an environment variable prefixed with TRAEFIK_.

Configuration Example¶

ENV

TRAEFIK_ENTRYPOINTS_WEB_ADDRESS=":80" TRAEFIK_ENTRYPOINTS_WEBSECURE_ADDRESS=":443" TRAEFIK_PROVIDERS_DOCKER=true TRAEFIK_API_DASHBOARD=true TRAEFIK_LOG_LEVEL="INFO" traefik

Helm¶

When deploying Traefik Proxy using Helm in a Kubernetes cluster, the install configuration is defined in a values.yaml file.

You can find the official Traefik Helm chart on GitHub

Configuration Example¶

values.yaml

ports:
  web:
    exposedPort: 80
  websecure:
    exposedPort: 443

additionalArguments:
  - "--providers.kubernetescrd.ingressClass"
  - "--log.level=INFO"

Helm Commands

helm repo add traefik https://traefik.github.io/charts
helm repo update
helm install traefik traefik/traefik -f values.yaml