Traefik 3.0 no middleware found in the cluster

[runningman84]

Traefik 3.0 no middleware found in the cluster

[mloiseleur]

@runningman84 It looks like the middleware are still using previous API Group, traefik.containo.us.
Starting with Traefik v2.10, a new API Group traefik.io has been introduced.

One can check easily which API Group is deployed

#  `traefik.containo.us` API Group
kubectl get middlewares.traefik.containo.us --all-namespaces
#  `traefik.io` API Group
kubectl get middlewares.traefik.io --all-namespaces

Both API Group are working with Traefik Proxy v2.10+.
traefik.io is the only API Group supported with Traefik Proxy v3.

Does this answer your question ?

[runningman84]

Rolling back to helm chart version: 27.0.2 (including traefik 2.11.2) made the svc-wss-headers middleware visible again in the dashboard but the authelia stuff is still not found. Is there some setting which auto discovers middlewares in all namespaces?

Btw. the traefik dashboard ingress route also come back.

There seems to be some breaking changes in the 28.0.0 helm chart / traefik 3.x release. It looks like all traefik crds are somehow broken (ingress route objects not appearing, middlewares lost....).

The cross namespace issue might be caused by this:
#1011

[nmengin]

Hello @runningman84,

It seems to be linked to Helm Chart modifications.
I transfer the issue to its repo.

[runningman84]

You are right using the correct api groups helps. But I think there are still other issues in the 3.x release because the ingress route objects (like the dashboard) is not viisible.

[mloiseleur]

It's the same for all other resources. All of them have to switch to the new API Group.

#  `traefik.containo.us` API Group
kubectl get ingressroutes.traefik.containo.us --all-namespaces
#  `traefik.io` API Group
kubectl get ingressroutes.traefik.io --all-namespaces

There are also (potentially many) other steps.

There is a complete migration guide, which details all those steps.

[mloiseleur]

I'm closing your issue, since there is nothing to do on the Chart at this point.
Feel free to re-open it (or open a new one), if needed.