100% Free Forever
AI-Powered Learning
Industry Expert Content
Certificates & Badges
Learn At Your Own Pace
DevOps

Traefik

By Traefik Labs

IntermediateTool4.7K learners

Traefik is a cloud-native reverse proxy and load balancer that automatically discovers services running in Docker, Kubernetes, and other orchestrators and configures routing for them, including automatic HTTPS via Let's Encrypt.

Definition

Traefik is a cloud-native reverse proxy and load balancer that automatically discovers services running in Docker, Kubernetes, and other orchestrators and configures routing for them, including automatic HTTPS via Let's Encrypt.

Overview

Unlike traditional reverse proxies such as Nginx, which typically need routing rules edited and reloaded manually as services change, Traefik watches the infrastructure it runs on directly — container labels in Docker, Ingress resources and CRDs in Kubernetes, or entries in Consul and other service registries — and updates its routing configuration automatically as services are added, removed, or scaled. Routing rules in Traefik are typically expressed as labels attached to a container or service (for example, specifying a hostname or path prefix that should route to it), rather than a centrally maintained configuration file. Traefik also integrates directly with Let's Encrypt, automatically requesting and renewing TLS certificates for the domains it routes, which removes a common source of manual operational work. Because of this dynamic, label-driven model, Traefik is popular in containerized and microservice environments where services come and go frequently, and it's often chosen as an Ingress controller for Kubernetes clusters or as the edge router in Docker Compose-based deployments, alongside tools like Envoy and Nginx in the broader cloud-native proxy landscape.

Key Features

  • Automatic service discovery from Docker labels, Kubernetes Ingress/CRDs, and Consul
  • Dynamic routing configuration that updates as services scale or change
  • Built-in automatic HTTPS certificate provisioning and renewal via Let's Encrypt
  • Middleware system for rate limiting, authentication, retries, and header manipulation
  • Load balancing across multiple backend instances of a service
  • Real-time dashboard for visualizing routers, services, and middlewares
  • Native Kubernetes Ingress Controller and Gateway API support

Use Cases

Acting as an edge router and reverse proxy for containerized microservices
Serving as a Kubernetes Ingress Controller with automatic TLS
Routing traffic in Docker Compose-based development and small production setups
Automatically issuing and renewing HTTPS certificates for many domains
Applying middleware like rate limiting or basic auth without touching application code
Load balancing traffic across dynamically scaling service instances

Frequently Asked Questions