Skip to content


How to install and configure the Traefik Hub agent.


The Traefik Hub agent supports two different installation methods, the Ingress Controller mode and the Sidecar mode.

Both Kubernetes Ingress Controller mode and the Sidecar mode pattern offer unique benefits.

Ingress Controller mode

Ingress Controller mode will install Traefik as Ingress Controller and will use it as a centralized entry point.

By leveraging Traefik as Ingress controller, the Traefik Hub agent utilizes the full potential of Traefik Proxy.

Key benefits:

  • ACME (Let's Encrypt) support
  • Extend the capability by leveraging plugins
  • Drop-in replacement for Traefik Enterprise

Using Traefik as Ingress Controller is the recommended way to get the most out of Traefik Hub.

Sidecar mode

The Sidecar pattern introduces an extra container, known as a sidecar container, alongside the main application container within a Pod.

This allows you to keep using your existing Ingress Controller, for example NGINX or Emissary (formerly Ambassador).

Compared to the Ingress Controller mode, the Sidecar approach has some limitations:

  • Higher latency since using a Sidecar means an extra network hop
  • Higher memory consumption
  • More difficult to maintain
  • Requires a deeper understanding of Kubernetes


Feature comparison

Feature Description Ingress Controller mode Sidecar mode
Keep exiting Ingress Keep using your existing Ingress Controller. No Yes
ACME support Support for ACME providers such as Let's Encrypt. Yes No
TLS termination The practice of terminating the Transport Layer Security (TLS) encryption at the Ingress level rather than letting it reach the individual Pods or Services within a Kubernetes cluster. Yes No
Drop-in replacement for any other Ingress Replace existing Ingress Controller for example, NGINX or Emissary. Yes No
Plugins Extend the functionality of Traefik Hub with plugins. Yes No

Installation methods

Choose one of the installation methods and continue to the installation docs.