When several applications share a cluster, incoming traffic needs to reach the right service using the intended hostname, path and protocol. Traefik is a reverse proxy and load balancer that reads supported configuration sources, including Kubernetes resources, to manage that routing. It can provide the entry point to services as they change. Select its Ingress or Gateway configuration deliberately and test the actual redirects, headers and encrypted connections required by the application before moving traffic.
Current guidance
Traefik has a current upstream Helm chart; review the controller release and required routing features separately from the historical chart.
Evaluate its Ingress and Gateway behavior against the protocols, middleware and policy features the application needs. A similarly named annotation from another controller is not a portable API. Record chart and app versions independently, and choose an application release within Traefik’s published support window. The current chart does not bundle Gateway API CRDs; install the CRDs required by the selected release before enabling that provider. When using Helm’s native CRD management, update Traefik CRDs according to the chart’s upgrade notes before running Helm upgrade.
During migration, compare redirects, rewrites, headers, TLS and long-lived requests through both endpoints. Retain the previous endpoint until traffic and certificate behavior are accepted.
Historical upstream link check · 2026-10-09
The recorded upstream address responded successfully (HTTP 200) on 2026-10-09. Link availability does not certify the historical installation instructions or current security support.
Website availability is separate from project, chart and image support. Use the current guidance and primary sources on this page to assess the distribution.
Historical Kubedex content
Preserved for context. Commands, versions, prices and results below reflect the original research.
Træfik is a modern HTTP reverse proxy and load balancer that makes deploying microservices easy. Træfik integrates with your existing infrastructure components (Docker, Swarm mode, Kubernetes, Marathon, Consul, Etcd, Rancher, Amazon ECS, …) and configures itself automatically and dynamically. Pointing Træfik at your orchestrator should be the only configuration step you need.
Overview
Imagine that you have deployed a bunch of microservices with the help of an orchestrator (like Swarm or Kubernetes) or a service registry (like etcd or consul). Now you want users to access these microservices, and you need a reverse proxy.
Traditional reverse-proxies require that you configure each route that will connect paths and subdomains to each microservice. In an environment where you add, remove, kill, upgrade, or scale your services many times a day, the task of keeping the routes up to date becomes tedious.
This is when Træfik can help you!
Træfik listens to your service registry/orchestrator API and instantly generates the routes so your microservices are connected to the outside world without further intervention from your part.
Features
- Continuously updates its configuration (No restarts!)
- Supports multiple load balancing algorithms
- Provides HTTPS to your microservices by leveraging Let’s Encrypt (wildcard certificates support)
- Circuit breakers, retry
- High Availability with cluster mode (beta)
- See the magic through its clean web UI
- Websocket, HTTP/2, GRPC ready
- Provides metrics (Rest, Prometheus, Datadog, Statsd, InfluxDB)
- Keeps access logs (JSON, CLF)
- Fast
- Exposes a Rest API
- Packaged as a single binary file (made with ❤️ with go) and available as a tiny official docker image
Supported Providers
- Docker / Swarm mode
- Kubernetes
- Mesos / Marathon
- Rancher (API, Metadata)
- Azure Service Fabric
- Consul Catalog
- Consul / Etcd / Zookeeper / BoltDB
- Eureka
- Amazon ECS
- Amazon DynamoDB
- File
- Rest
Sources & further reading
Spotted something that needs another look?
Help improve this page →