Traefik Mesh
Traefik Mesh (formerly Maesh) is a lightweight, non-invasive service mesh built on top of Traefik Proxy for Kubernetes. It provides automatic traffic management, observability, and security for microservices without requiring sidecar containers. Traefik Mesh is compliant with the Service Mesh Interface (SMI) specification and supports HTTP, TCP, and UDP traffic modes, traffic splitting, access control via TrafficTarget, rate limiting, circuit breaking, and retries. The project is effectively dormant: the last released version is v1.4.8 (2022-08-19), and commit activity since then has been limited to CI and documentation maintenance. The GitHub repository is not formally archived as of this profile date and there is no official deprecation banner on the project's README or documentation site, but the lack of feature releases for nearly four years and the absence of an SMI-compatible successor inside Traefik Labs' product line (Traefik Hub is positioned as Kubernetes-native API management, not a service mesh) make this an unmaintained project for practical purposes.
Traefik Mesh publishes 1 API on the APIs.io network: Controller API. Tagged areas include Kubernetes, Service Mesh, Open Source, SMI, and Traffic Management.
The Traefik Mesh catalog on APIs.io includes 1 machine-runnable capability, 1 JSON-LD context, and 1 Spectral governance ruleset.
Traefik Mesh’s developer surface includes documentation, engineering blog, changelog, and 13 more developer resources.
APIs
Traefik Mesh Controller API
The Traefik Mesh Controller API provides internal debugging and status endpoints for the Traefik Mesh controller pod. It exposes the current dynamic configuration built by the c...
Capabilities
Traefik Mesh Operations
Unified workflow capability for operating and debugging a Traefik Mesh service mesh deployment. Combines controller configuration, topology inspection, and node health monitorin...
Run with NaftikoFeatures
No sidecar containers required; uses per-node Traefik Proxy instances.
Full support for Service Mesh Interface (SMI) specification including TrafficSplit, TrafficTarget, HTTPRouteGroup, and TCPRoute.
Retry, circuit breaking, rate limiting, and traffic splitting for HTTP services.
Transparent proxy support for TCP and UDP traffic in addition to HTTP.
All traffic forbidden by default unless explicitly allowed via SMI TrafficTarget resources.
Route traffic subsets to different service versions using SMI TrafficSplit.
Configure mesh behavior per service via Kubernetes annotations.
Easy deployment and configuration via official Helm chart.
Use Cases
Gradually shift traffic to new service versions using SMI TrafficSplit.
Enforce zero-trust networking with SMI TrafficTarget ACL mode.
Inspect live mesh configuration, topology, and node readiness via controller API.
Apply retries, circuit breakers, and rate limits without changing application code.
Integrations
Uses Traefik Proxy as the data plane proxy on each Kubernetes node.
Native Kubernetes integration via Custom Resource Definitions and annotations.
Implements Service Mesh Interface specification for interoperability.