Choosing TrafficSplit for Canary Deployments in Traefik Mesh
A decision guide that compares TrafficSplit with Istio‑based alternatives, explains trade‑offs, and shows how to implement and validate a weight‑based canary rollout.
Loading…
ReadMeFeed / Community knowledge
Traefikmesh
Real questions. Useful conversations. Find the people who know your stack.
Traefikmesh
Developer tools · #traefikmesh
kubernetesUsing Traefik Mesh TrafficSplit for Safe Canary Deployments
Learn how Traefik Mesh TrafficSplit enables weighted canary releases without code changes, including setup, verification via Prometheus, and key limitations.
Choosing Between Operator-Managed and Manual Traefik Mesh Configurations
Decide between Traefik Mesh Operator and manual CRD configuration. Learn how to balance mTLS automation against granular control and implement weighted traffic splitting.
Using Traefik Mesh Weighted Traffic Splitting for Safe Canary Deployments
Learn how to shift a fraction of traffic to a new service version with Traefik Mesh’s TrafficSplit resource, verify the split with Prometheus metrics, and understand the operational constraints.
Architecting Service-to-Service Trust with Traefik Mesh Sidecars
Learn how Traefik Mesh uses sidecar proxies and mTLS to eliminate implicit trust in Kubernetes clusters, moving from IP-based security to a Zero Trust identity model.
Traefik Mesh ClusterMesh Resource vs Pod Annotations: Sidecar Injection Mode Conflict
Injection Mode Conflict at the Pod Boundary When deploying workloads into a Traefik Mesh cluster, the sidecar injection behavior is governed by a ClusterMesh resource that defines a cluster-wide or namespace-scoped policy. Individual pods can also carry mesh.* annotations that appear to request a specific injection mode. The documentation does not clearly st
Implement weight‑based traffic splitting in Traefik Mesh with TrafficSplit
Guide to route a percentage of requests to different service versions using a TrafficSplit custom resource in Traefik Mesh.
Traefik Mesh Gateway mTLS Without Sidecars Across Clusters
Traefik Mesh uses gateway proxies and automated mTLS to secure multi-cluster service traffic without per-pod sidecars, with routing controlled via TrafficRoute CRDs.
Ingress Gateway TLS Termination defaults: preventing accidental public access
Ingress Gateway TLS Termination Traefik Mesh’s ingress gateway accepts HTTP traffic by default unless TLS is explicitly configured. This default behaviour can expose services to the public internet if operators forget to enable TLS termination. The documentation does not state that TLS must be configured for all public endpoints, leaving an ambiguity in the