-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Description
Hi 👋
We are facing a TrafficRoutingError when using Argo Rollouts v1.8.3 with Traefik v3 CRDs (traefik.io/v1alpha1).
Although all required Traefik CRDs and resources exist and are valid, the rollout controller fails with:
TrafficRoutingError: the server could not find the requested resource
This looks like an incompatibility between argo-rollouts v1.8.3 and Traefik v3 API group (traefik.io).
Environment
Argo Rollouts version: v1.8.3 (stable)
Traefik CRDs: traefik.io/v1alpha1 (Traefik v3)
argoproj/argo-rollouts:v1.8.3
Rollout spec (Traefik traffic routing)
strategy:
canary:
stableService: interactions-cases-management-stable
canaryService: interactions-cases-management-canary
trafficRouting:
traefik:
weightedTraefikServiceName: interactions-cases-management
Existing TraefikService (verified)
apiVersion: traefik.io/v1alpha1
kind: TraefikService
metadata:
name: interactions-cases-management
namespace: digital-ns
spec:
weighted:
services:
- name: interactions-cases-management-stable
port: 8080
- name: interactions-cases-management-canary
port: 8080
CRDs are present:
traefikservices.traefik.io
ingressroutes.traefik.io
kubectl api-resources confirms availability.
Logs from argo-rollouts controller
time="2025-12-22T13:19:37Z" level=warning msg="the server could not find the requested resource" event_reason=TrafficRoutingError namespace=digital-ns rollout=interactions-cases-management
time="2025-12-22T13:19:37Z" level=error msg="rollout syncHandler error: the server could not find the requested resource"
Expected behavior
Argo Rollouts should be able to:
recognize TraefikService in traefik.io/v1alpha1
update weights in spec.weighted.services[]
proceed with canary steps without TrafficRoutingError
Actual behavior
Rollout reconciliation fails
Controller reports requested resource not found
Canary traffic routing never progresses
Question
Is Traefik v3 (traefik.io/v1alpha1) officially supported in argo-rollouts v1.8.3?
If not:
which version introduces proper support?
is there a compatibility matrix for Traefik major versions vs argo-rollouts?