Using Traefik Mesh TrafficSplit for Canary Releases in Kubernetes
Learn how to use Traefik Mesh TrafficSplit to perform weighted canary releases in Kubernetes, with a concrete example, verification steps, and limitations.
Loading…
ReadMeFeed / Community knowledge
#traefik-mesh
Real questions. Useful conversations. Find the people who know your stack.
traefikmesh
kubernetesUsing Traefik Mesh TrafficSplit for Weighted Canary Deployments
Learn how Traefik Mesh implements the SMI TrafficSplit resource for weighted traffic splitting, including a corrected YAML example, verification guidance, and important limitations.
Canary Deployments in Traefik Mesh: HTTPRoute Traffic Splitting Without Sidecars
Deploy a canary in Traefik Mesh with HTTPRoute traffic splitting. Learn how the sidecar‑less architecture works, see a concrete example, and weigh the trade‑offs before you roll out your next microservice update.
Unlock Zero‑Config Mutual TLS with Traefik Mesh: Automatic Certs, Rotation, and Real‑Time Observability
Traefik Mesh gives micro‑services a zero‑config mutual TLS layer by auto‑issuing X.509 certificates in sidecars. Learn how to enable it, view metrics, and weigh CPU overhead and rotation limits in this hands‑on guide.
Implementing Zero Trust with Traefik Mesh Automatic mTLS
Learn how Traefik Mesh automates mTLS for service-to-service security, including configuration for strict mode and how to troubleshoot sidecar injection failures.
Traefik Mesh sidecar resource limits not scaling with traffic
Traefik Mesh Sidecar Scaling Goal Reduce operational costs for a low‑traffic microservice by minimizing the CPU and memory overhead introduced by the Envoy sidecar injected by Traefik Mesh. Constraints and Uncertainty Each pod receives a sidecar by default, and its resource requests and limits can be tuned via pod annotations or namespace defaults. The Mesh
Traefik Mesh: Rollback safety after schema changes
Traefik Mesh currently applies configuration changes directly to Kubernetes CRDs, propagating them to Envoy sidecars without a transactional system. This means that a schema update that is syntactically correct but semantically invalid can immediately destabilize services, and the prior configuration state is not preserved inside Traefik Mesh. Because the me