Traefik Mesh
Traefik Mesh is an open-source service mesh for Kubernetes that routes traffic through proxy endpoints on each node and runs its controller in a dedicated pod.
What Traefik Mesh is
Traefik Mesh is an open-source service mesh for Kubernetes that routes traffic through proxy endpoints on each node and runs its controller in a dedicated pod. It does not use sidecar containers, and existing services stay outside the mesh until explicitly added through Traefik Mesh service names. Teams can configure services with annotations or Service Mesh Interface (SMI) objects. Traffic controls include retries, circuit breakers, rate limits, and SMI traffic splitting; ACL mode can require authorization between resources. A built-in debugging API is accessed through the controller pod rather than exposed as a service. Installation is documented through a Helm chart and requires Kubernetes, CoreDNS or KubeDNS, and Helm v3. The documentation recommends conformant Kubernetes environments and reports use on AWS, GKE, Azure, and DigitalOcean. Its compatibility page lists Kubernetes 1.21, 1.22, and 1.23 as the latest supported minor versions. Traefik Mesh does not provide mutual TLS or implement the SMI Traffic Metrics specification. It is free and self-hosted for Kubernetes.
Good
- Open-source and free to use.
- Routes traffic without sidecar containers.
- Services can be added selectively.
- Supports retries, circuit breakers, and rate limits.
- Supports SMI traffic splitting and ACL mode.
Watch out
- Requires Kubernetes, CoreDNS or KubeDNS, and Helm v3.
- Does not provide mutual TLS.
- Does not implement SMI Traffic Metrics.
- Latest supported minor versions listed are 1.21–1.23.
Who it suits
Traefik Mesh suits teams running Kubernetes that want to add services to a mesh selectively and configure traffic controls. Users should be comfortable with its Kubernetes, DNS, and Helm prerequisites.
Verdict
Traefik Mesh offers a sidecarless approach with selective service inclusion and traffic policies for Kubernetes. Its prerequisites and lack of mutual TLS and SMI Traffic Metrics support are important limits to weigh.
Plans and prices
From Traefik Mesh's own pricing page, checked 9 Oct 2026.
| Plan | Price | What it gives you |
|---|---|---|
| Traefik Mesh | Free | Open source; requires Kubernetes 1.11+, CoreDNS/KubeDNS, and Helm v3 |
The facts
Each one read from Traefik Mesh's own pages, with the date it was checked.
What it does
- Access control
- Optional ACL mode forbids traffic unless it is explicitly allowed through an SMI TrafficTarget.checked 9 Oct 2026
- Architecture
- It routes traffic through proxy endpoints on each node and runs its controller in a dedicated pod, without sidecar containers.checked 9 Oct 2026
- Cloud compatibility
- The installation documentation says it runs on most public clouds, including AWS, GKE, Azure, and DigitalOcean.checked 9 Oct 2026
- Compatibility limit
- The compatibility page lists Kubernetes 1.21, 1.22, and 1.23 as the currently supported latest minor versions and says general functionality is not guaranteed for older versions.checked 9 Oct 2026
- Configuration
- Services can be configured with Kubernetes annotations or Service Mesh Interface objects.checked 9 Oct 2026
- Debug API
- A built-in debugging API is accessed through the controller pod and is not exposed via a service for security reasons.checked 9 Oct 2026
- Installation
- The supported installation method is Helm using official releases; source installation is intended for development or contributing and may not be supported.checked 9 Oct 2026
- Kubernetes compatibility
- The compatibility page lists Kubernetes versions 1.21, 1.22, and 1.23 as its latest three supported minor versions and says older versions may not have general functionality guaranteed.checked 8 Oct 2026
- Metrics limitation
- Traefik Mesh does not implement the SMI Traffic Metrics specification.checked 9 Oct 2026
- Opt-in
- Existing services are unaffected until they are explicitly added to the mesh.checked 8 Oct 2026
- Opt-in behavior
- Existing services are unaffected by default; services join the mesh when accessed through Traefik Mesh service names.checked 9 Oct 2026
- Prerequisites
- The documented prerequisites are Kubernetes 1.11+, CoreDNS or KubeDNS, and Helm v3.checked 9 Oct 2026
- Purpose
- Traefik Mesh is a lightweight service mesh designed to be straightforward to install and use in a Kubernetes cluster.checked 9 Oct 2026
- Security limitation
- The documentation states that Traefik Mesh does not provide mutual TLS.checked 9 Oct 2026
- SMI support
- Traefik Mesh supports the Service Mesh Interface specification.checked 8 Oct 2026
- Supported environments
- The documentation recommends conformant Kubernetes environments and reports use on AWS, GKE, Azure, and DigitalOcean.checked 8 Oct 2026
- Traffic controls
- Configuration supports traffic types, retries, circuit breakers, rate limits, and SMI traffic splitting.checked 9 Oct 2026
- Traffic examples
- The examples configure both HTTP and TCP services for access through Traefik Mesh.checked 8 Oct 2026
The company
- Company
- Traefik Labs says it was founded in 2016 and describes its mission as helping organizations adopt and scale cloud-native architectures.checked 8 Oct 2026
- Founded
- 2016checked 28 Sep 2026
- Headquarters
- Traefik Labs' privacy policy identifies its registered office as 132 rue Bossuet, 69006 Lyon, France.checked 8 Oct 2026
- Maker
- Traefik Labs says it was founded in 2016.checked 9 Oct 2026
Alternatives to Traefik Mesh
- 1
Kuma
Free planOpen sourceWebAPILinuxmacOS7.5Free plan - 2
AWS App Mesh
Free planWebAPILinuxmacOS7.1Free plan - 3
Network Service Mesh
Free planOpen sourceAPILinuxSelf-hosted7.0Free plan - 4
Oracle Cloud Infrastructure Container Registry
Free planWebAPILinux7.0Free plan - 5
Buoyant Enterprise for Linkerd
Free planWebLinuxSelf-hostedWindows6.3Free plan - 6
Istio
Free planLinuxmacOSSelf-hosted6.2Free plan