After three months of intensive development and two release candidates, Traefik Labs announced the general availability of Traefik 3.2โjust in time for Halloween. This “Munster” release brings thrilling new features, key enhancements, and remarkable performance boosts.
Speaking of that, we’re actually talking about the new Fast Proxy engine, designed to enhance routing performance through a zero-allocation pipeline, delivering an impressive 50% performance boost compared to the standard engine.
It significantly reduces latency while increasing throughput, meaning you can now expect around 50% more requests per secondโperfect for environments where every millisecond counts.
However, keep in mind that this new feature is still experimental. To enable it, simply add the following configuration:
experimental:
fastProxy: {}Code language: YAML (yaml)Being cloud-native by nature, the new release continues to strengthen support for the Kubernetes Gateway API. In light of this, Traefik 3.2 is now fully compatible with Gateway API v1.2, bringing new features such as GRPCRoute and TLSRoute, along with enhancements for HTTPRoute.
For instance, the newly introduced GRPCRoute type allows you to define the routing behavior for gRPC requests, adding more flexibility to manage this widely adopted RPC framework within Kubernetes.
Moreover, Traefik 3.2 also supports TLSRoute, enabling TLS multiplexing via Server Name Indication (SNI), cementing the software’s position as one of the most versatile solutions for managing Kubernetes traffic.
Additionally, the new version includes several updates to ACME certificate management, such as allowing different email addresses for certificate resolvers and supporting custom Certificate Authorities. BasicAuth is now also supported for Docker and Swarm endpoints, making Traefik more secure and flexible for container-based deployments.
Traefikโs middlewares have also received various updates. The “ipStrategy” now supports IPv6 subnets for rate limiting, has new compression options, and has improved logging capabilities, including the ability to log trace IDs for better observability.
We can’t fail to mention that an option to mirror the full request body in HTTP mirroring has been added, providing greater insight into requests without compromising data integrity.
Lastly, this release addresses various usability issues, particularly about Kubernetes Gateway API features. Notable fixes include ensuring the uniqueness of Traefik resource names in the Gateway API and preserving filter orders in GRPCRoute.
Check out the release announcement or look at the changelog for the full list of all novelties in Traefik 3.2.
