You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The TraefikService resources that Flagger creates use the traefik.containo.us Kubernetes API group that has been deprecated in Traefik v3.
To Reproduce
Create a Flagger Canary resource that uses the traefik provider.
Upgrade Traefik to v3.
Observe the following errors in Traefik logs:
ERR error="the service \"default-podinfo-canary@kubernetescrd\" does not exist" entryPointName=web routerName=web-default-podinfo-canary-3dfb9b2aaefc944f017e@kubernetescrd
Looking at the TraefikService manifest that Flagger creates, it uses the traefik.containo.us Kubernetes API group that has been deprecated in the latest Traefik release:
Looks like it does. The docs have a warning about the support being experimental for now, but I'm not sure what implications that would have for Flagger.
Describe the bug
The
TraefikService
resources that Flagger creates use thetraefik.containo.us
Kubernetes API group that has been deprecated in Traefik v3.To Reproduce
traefik
provider.Looking at the
TraefikService
manifest that Flagger creates, it uses thetraefik.containo.us
Kubernetes API group that has been deprecated in the latest Traefik release:Expected behavior
Flagger creates
TraefikService
resources with the newtraefik.io
Kubernetes API group.Additional context
The text was updated successfully, but these errors were encountered: