Skip to content

Routing Configuration Reference

Configure Routing in TraefikEE

To configure the routing in TraefikEE (after installation), deploy a normal Traefik CLI configuration using the traefikeectl deploy command line.

Important

Please note that, at the moment, only command line arguments are supported, TOML configuration files are not.

You can find more information about the normal Traefik command line arguments on the following pages:

Examples

Dynamic Routing Configuration from Kubernetes

Configure TraefikEE with the following:

  • Use Kubernetes as a provider for getting dynamic routing configuration
  • Enable a default entrypoint named http to listen for incoming HTTP requests on the port 80
traefikeectl deploy --kubernetes

Specific Configuration for Kubernetes

Configure TraefikEE with the following:

traefikeectl deploy --kubernetes \
    --kubernetes.namespaces=traefikee,production

Listen on a Custom Entrypoint

Configure TraefikEE with the following:

traefikeectl deploy --kubernetes \
    --entryPoints='Name:internal Address::8888' \
    --defaultentrypoints=internal

Important

When using an orchestrator, TraefikEE's installation creates 2 "network services" for:

  • HTTP on port 80
  • Eventually HTTPS on port 443.

If you want a custom entrypoint a different port, then you must configure the network service by yourself. This "service" allows incoming requests to reach TraefikEE's data plane elements on the custom entrypoint's port.

In the case of Kubernetes, create a "Kubernetes Service" targeting all the nodes of TraefikEE's data plane.

Listen on the HTTPS Entrypoint with Let's Encrypt (ACME) Dynamic Certificates

Configure TraefikEE with the following:

traefikeectl deploy --kubernetes \
    --entryPoints='Name:https Address::443 TLS' \
    --defaultentrypoints=https \
    --acme.entryPoint=https \
    --acme.email=ssl-admin@company.org \
    --acme.tlsChallenge