This section clarifies terms specific to TraefikEE.
TraefikEE comes with two Command-Line Interface tools:
The first is the traefikee binary itself, and the latter helps you manage your traefikee cluster (you can see it as a remote).
Controller(s) are TraefikEE instances with components that are responsible for creating and managing the cluster. They are also responsible for synchronizing configuration changes with the proxies.
Proxy(s) are TraefikEE instances with components that are responsible for handling the routing of incoming requests. It's components are configured by the controller components.
Configuration of a TraefikEE cluster, for example the cluster license and the number of controllers and proxies.
Static Configuration is applied to controllers and proxies and contains information such as the providers and entrypoints. TraefikEE uses the same static configuration as Traefik with a few additions, such as Authentication Sources.
Dynamic Configuration is gathered from orchestrators and contains the definitions for resources like routers, services and middleware. See the dynamic configuration reference for more information.
A cluster command is a request sent to the TraefikEE cluster. The request will be handled by one of the controller but will update/request the state of the whole cluster.
Cluster commands are documented in the
traefikee Command Line Reference section.
In the documentation,
infrastructure components refers to third-party tools like orchestrators and key-value stores.
We often mention the quorum in the documentation. In TraefikEE, it is the minimum number of controller of a cluster that must be up in order for the cluster to be healthy. For more information on the amount of controller your cluster should have, take a look at this section of the documentation.
ACME stands for 'Automatic Certificate Management Environment' and is protocol that can be used to interact with certificate authorities like Let's Encrypt.
Static and Dynamic Configuration¶
Please refer to the Traefik configuration overview.
An Authentication Source is a source (such as an LDAP server) with which TraefikEE middleware can authenticate the validity of a request.