New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kubernetes provider logs errors during object loading #3667
Comments
This is absolutely bad user experience which costed me (and others) hours to find the issue. I had some missing certs, so I got a invalid cert error in browser and saw in the logs that the cert is missing. After I fixed this, I still got the error in the logs. I diged through all the other (open and closed) bugs with this error message, altered my traefik installation, reinstalled traefik, manually checked the service role, reinstalled the cert - all the time getting this wrong error. |
Am having the same issue with aks 1.14.8 Is there an update on this issue? |
Although this was an issue in v1, we are using a different client and a different provider process in v2. Note that this issue did not affect performance, it was a logging anomaly. For this reason, we are going to be closing this issue. If the issue occurs in v2, we will open a new issue, and have debugging data in that new issue. |
False error still exists in Traefik 2.05. It's not a timing issue. The secret existed in my kubernetes namespace long before the traefik pod started. Besides that all works fine. It's really just a false log message.
Setting in Traefik config:
I'm using let's encrypt to create the secret |
Hello guys, I'm trying to apply secure dashboard in a Kubernetes scenario using Traefik v2.1, but something it's not ok and I think it's the same error.
But I'm getting this log:
When i try to see if the secret is there with kubectl it works, but looks like traefik doesn't find it, and I guess it's because traefik is trying to find Anyone with this error too? |
This comment has been minimized.
This comment has been minimized.
I found default tls setting source code
I give up |
@ldez I cannot see how the updated doc is related to the fact that traefik logs a false error message. Maybe you should add to https://docs.traefik.io/v2.1/providers/kubernetes-ingress/ something like "if you see secret not found errors, ignore it, it's a false error" if you don't intent to fix this. |
This is still an issue in |
Traefik version 2.1.4 built on 2020-02-06T17:10:06Z |
Closed by #6364. |
Do you want to request a feature or report a bug?
Bug
What did you do?
Create an ingress with a TLS cert in a secret
What did you expect to see?
Nice, clean, happy logs.
What did you see instead?
If applicable, please paste the log output in DEBUG level (
--logLevel=DEBUG
switch)This is the cause of the error logs in #3402, as the secrets do exist, they are just not sync'd yet.
The text was updated successfully, but these errors were encountered: