Glossary

This section clarifies terms specific to TraefikEE.

CLI

TraefikEE comes with two Command-Line Interface tools: traefikee and traefikeectl. The first is the traefikee binary itself, and the latter helps you manage your traefikee cluster (you can see it as a remote).

Note

You can read the full documentation of traefikee and traefikeectl to learn more about what you can achieve with them.

Control Plane

The control plane consists of components responsible for managing the configuration. Components located in the control plane configure components located in the data planes.

Note

You can find more information about the control plane concept on Wikipedia or by readying the RFC3746 and RFC3746.

Control Plane Node(s)

A control plane node is an instance of TraefikEE that belongs to the control plane.

Cluster Command

A cluster command is a request sent to the TraefikEE cluster. The request will be handled by one of the control nodes but will update/request the sate of the whole cluster.

Note

The cluster commands are documented in the traefikee Command Line Reference section.

Data Plane

Components in the data plane handle the routing of the incoming requests. Components in the data plane are configured by components located in the control planes.

Note

You can find more information about the data plane concept on Wikipedia - Forwarding plane or by reading the RFC3746.

Data Plane Node(s)

A data plane node is an instance of TraefikEE that belongs to the data plane.

Infrastructure Components

In the documentation, infrastructure components refers to third-party tools like orchestrators and key-value stores.

Quorum

We often mention the quorum in the documentation. In TraefikEE, it is the minimum number of control nodes of a cluster that must be up in order for the cluster to be healthy. For more information on the amount of control nodes your cluster should have, take a look at this section of the documentation.