Traefik v3.0 breaks existing cert-manager
integrations
#10702
Labels
area/acme
area/rules
kind/bug/possible
a possible bug that needs analysis before it is confirmed or fixed.
Welcome!
What did you do?
I was using Traefik v2 for a long time together with
cert-manager
inside Kubernetes.For my usual routes, I am using the
IngressRoute
CRD which works perfectly fine again after I followed the migration guide.However, all my existing
cert-manager
integrations and automatic certificate renewals in the whole cluster stopped working silently. Theacme-solver
s created by thecert-manager
are default Kubernetes Ingress and they have not changed at all. I just noticed this today after a certificate could not be renewed for a very long time and gut stuck.The Ingress they create is nothing special and as mentioned this has not changed, I have not done any other updates to the cluster than Traefik v3.0 since this problem came up.
What did you see instead?
It seems that the Ingress route is simply ignored. I tried by removing all existing
IngressRoutes
in the same namespace and only leaving the auto-created Ingress for a testing certificate. I tried to manually debug the whole flow and see where it gets stuck and it was for sure Traefik v3.0.I am using the Helm Chart to deploy Traefik and
providers.kubernetesIngress.enabled
is set to true and is the default value in there.The auto-created spec looks like this:
I usually have https-redirects for each host name and as soon as I added the IngressRoute again, I got back the HTTP 301 from it, even though I should have gotten the acme challenge. But as mentioned even without this redirect route I alway received a
404 page not found
.I am using a very nasty workaround everywhere now so I can at least get my certificates renewed. This is simply ignoring the auto-created Ingres resources and I manually added the following IngressRoute definitions to at least make it working again:
This solution is very brittle and tedious though.
I was very lucky that the failed certificate over night was on some staging environment instead of production.
What version of Traefik are you using?
Helm Chart version:
traefik-28.0.0
App-Version:
3.0.0
What is your environment & configuration?
Custom
values.yaml
:If applicable, please paste the log output in DEBUG level
No response
The text was updated successfully, but these errors were encountered: