Traefik has released v3.7.10, a patch version focused on stability and reliability, particularly for Kubernetes users and authentication handling. This release addresses several key bugs and bumps essential dependencies to improve compatibility and performance. Below are the notable changes.
Key Fixes and Updates
- ACM and dependencies: Bumped
github.com/go-acme/lego/v5to v5.3.1 to fix issues with certificate issuance ( #13547 ). This ensures better ACME protocol compliance. - Authentication: Fixed a singleflight key collision in the authentication middleware ( #13572 ), preventing potential cache misses that caused repeated auth requests.
- Kubernetes Gateway API: Avoided router name collisions in the Gateway API provider ( #13580 ), which could cause routes to be incorrectly merged or overwritten.
- Tracing: Bumped
github.com/DataDog/dd-trace-go/v2to 2.8.1 for improved Datadog tracing support ( #13530 ). Also updatedgolang.org/x/textto v0.40.0 andgolang.org/x/netto v0.57.0 ( #13574 ), fixing potential security issues in networking and text processing. - Kubernetes CRD Provider: Fixed a cross-namespace service reference check ( #13573 ), ensuring that services referenced in IngressRoute definitions must be in the same namespace unless explicitly allowed.
- Compression: Bumped
github.com/klauspost/compressto v1.18.7 ( #13587 ), enabling better compression performance and reduced memory usage. - Gateway API: Bumped sigs.k8s.io/gateway-api to v1.6.1 ( #13589 ), aligning with the latest Gateway API specification and ensuring compatibility with newer Kubernetes versions.
Documentation
- Clarified the interaction between auth-url and rewrite-target annotations on the
ingress-nginxprovider ( #13607 ), helping users configure authentication and URL rewriting without unexpected behavior.
This release is crucial for developers running Traefik in Kubernetes environments, as it resolves race conditions and validation issues that could lead to routing errors or security gaps. The dependency updates, especially for ACME and networking, also reduce vulnerabilities and improve stability. For production users, upgrading to v3.7.10 is recommended to benefit from these fixes. Always test in a staging environment before rolling out.
Source: https://github.com/traefik/traefik/releases/tag/v3.7.10