-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Packaged Traefik 2.9.4 has incorrect access logs #7301
Comments
Thanks for the report. We'll likely bump it as part of our next release cycle. |
This issue was not reproducible in my standalone deployment but I was able to confirm the newer image versions used. I think we can just treat this as a validation for the version bump. COMMIT=8f450bafe1cad0e962e521d56eb74a38a73722c7 $ kg pod/traefik-899bbd849-v4gpb -o yaml -n kube-system | grep -i image
$ k logs -l app.kubernetes.io/name=traefik -n kube-system
I did not observe the same behavior from the initial issue on v1.27.1+k3s1 with the listed Traefik version. Tried to reproduce on v1.26 instead $ kg pod/traefik-fb68c966d-7njrg -o yaml -n kube-system | grep -i image
$ k logs -l app.kubernetes.io/name=traefik -n kube-system
v1.26.4+k3s1 did not show the missing status codes $ kg pod/traefik-6b695786fd-xpxb8 -o yaml -n kube-system | grep -i image
10.42.0.1 - - [11/May/2023:18:19:52 +0000] "GET /ping HTTP/1.1" 200 2 "-" "-" 24 "ping@internal" "-" 0ms
k3s version v1.26.4+k3s1 (8d0255a)
helmchartconfig.helm.cattle.io/traefik created
NAMESPACE NAME READY STATUS RESTARTS AGE
10.42.0.1 - - [11/May/2023:18:23:28 +0000] "GET /ping HTTP/1.1" 200 2 "-" "-" 7 "ping@internal" "-" 0ms
k3s version v1.26.3+k3s1 (01ea3ff)
|
Environmental Info:
K3s Version:
Node(s) CPU architecture, OS, and Version:
Cluster Configuration:
Describe the bug:
The access logs of Traefik (the packaged 2.9.4 version) do not have all status codes recorded correctly. Some status codes are recorded as 0. Traefik maintainers said they had a bug before 2.9.5 and suggested to try 2.9.10 (see issue). My try of 2.9.10 seemed to be good. k3s should update the packaged traefik version soon.
Steps To Reproduce:
Expected behavior:
The access log should record the status codes:
Actual behavior:
Some log lines has 0 status codes:
Additional context / logs:
Tried to update traefik to 2.9.10 by changing the manifest above to:
The access logs seemed correct.
The text was updated successfully, but these errors were encountered: