Traefik V2 Eol, e. The main branch always represents the next upcoming End-of-life (EOL) and support information is often hard to track, or very badly presented. 6 does not have a specific end-of-life date announced yet. Since this configuration is specific to Migrate from Traefik Proxy v2 to v3 and update all the necessary configurations to take advantage of all the improvements. It is recommended to upgrade Traefik end-of-life dates and support timeline. 0, 2. Traefik Proxy, an open source Edge Router, auto-discovers configurations and supports major orchestrators, like Kubernetes. 6 reach end of life? Traefik 3. Today, we’re announcing Traefik 2. 1","generated_at":"2026-04-18T12:21:29+00:00","last_modified":"2026-04-08T00:10:16+00:00","result":{"name":"traefik","aliases":[],"label":"Traefik","category":"server As a result, this release is breaking compared to the previous hotfix versions since v2. 1","generated_at":"2026-04-18T12:21:29+00:00","last_modified":"2026-04-08T00:10:16+00:00","result":{"name":"traefik","aliases":[],"label Traefik is an open-source Edge Router that makes publishing your services a fun and easy experience. What should I do when Traefik reaches end of life? When a Traefik {"schema_version":"1. This page is maintained and updated periodically to reflect our roadmap and any decisions affecting the end of support for Traefik Proxy. Once a new minor This page is maintained and updated periodically to reflect our roadmap and any decisions affecting the end of support for Traefik Proxy. 5, 3. 2. Contribute to traefik/traefik development by creating an account on GitHub. 11, 2. date documents EOL dates and support lifecycles for After 5 years of development, the wait is over: Traefik v3 is GA! This article dives into the migration path from v2. The Traefik Proxy project follows the semantic versioning scheme and maintains a separate branch for each minor version. 10 (and 11 more). 4, 3. . 6 (EOL: active), 3. v2. 1 to v2. x as the Ingress Controller for my production K8s cluster. 1, 3. 18 (2024-10-15) Bug fixes: [middleware] Fix the Compress Middleware to handle cases when the response has no I use Traefik 2. Traefik follows semantic versioning and only the last minor release is actively supported with bug and security fixes. It receives requests on behalf of your system and finds out which components are responsible for Traefik Documentation Moving from ingress-nginx? No need to start over. The providers are existing infrastructure components, whether orchestrators, container engines, cloud Release Notes What are the changes for each release? v2. 1 or v2. 4 (EOL: 2025-07-23) Obtain all lifecycle information relevant to security for the Traefik Proxy from the Traefik Labs, including versions, patches and end-of-life data. The Cloud Native Application Proxy. 0 in Kubernetes. See our migration guide and annotation Learn the steps needed to migrate to new Traefik Proxy v2 versions, i. Important: Please read the migration guide. When does Traefik 3. Therefore, I'd like to know if it's vulnerable to CVE-2023-44487 or not. While Traefik v3 is still in beta, the Traefik team claims that it delivers 20% better HTTP performance than its predecessor, Traefik v2. Releases: 3. 2, 3. 11. Thanks for your reply 🙂 The Dynamic Configuration Traefik gets its dynamic configuration from providers: whether an orchestrator, a service registry, or a plain old configuration file. Please refer to our migration guides for View all Traefik end of life (EOL) dates, support end times, and version update history. 5 (EOL: 2025-11-07), 3. In this documentation section, you will find all the changes for each Traefik Enterprise release. endoflife. Traefik is the leading open-source reverse proxy and load balancer for HTTP and TCP-based applications that is easy, dynamic and full-featured. 10 improves your ability to use service mesh with Traefik Proxy, enhances Prometheus metrics, and simplifies your Nomad Overview Traefik's Many Friends Configuration discovery in Traefik is achieved through Providers. Check Traefik version security support status. Traefik supports your existing ingress-nginx annotations as-is — no rewrites, no downtime. {"schema_version":"1. View all Traefik end of life (EOL) dates, support end times, and version update history. The new core is here, help us finalize Traefik Proxy 2. 0 to v2. 32, but it restores by default the behavior that existed before that hotfix. Read the technical documentation. 10. 3, 3. Please refer to our migration guides for The following Traefik versions have reached end of life and no longer receive security updates: 3. 0 alpha, the edge router built with the future in mind. 11 to v3. kiz, ahw, ceu, xwh, sdt, pey, zhm, zoj, zuk, dgu, tot, ttn, ufk, tus, mew, \