🎊 Introducing the Public Roadmap for Traefik Proxy 3.0!

As an open-source project started by the community, for the community, we believe that open governance is not only in the DNA of Traefik, but it is a vital everyday practice.

As we approach our next major release, Traefik Proxy 3.0, we are super excited to honor our roots and open our roadmap to the public and invite community members to take a much larger role in the direction of Traefik Proxy.

We leaned heavily into community requests and UX improvements to choose the feature set for Traefik Proxy 3.0, which will be released in at least 2 betas. The first beta release will focus on breaking fixes that dramatically increase performance and improve configuration. The second beta will focus on enhancing Kubernetes ingress performance and certificate management (including TLS ACME cert management).

We see and value how much our community wants to be involved in the process of designing and building features for Traefik Proxy and are identifying features that we would like to incorporate and require the help of our community to build. You will see these features tagged with contributor/wanted to let you know that if you work on issues, our team will be available for design help, and you will be bumped to the front of the review queue (even in front of team-built PRs!).

You can find our Public Roadmap on GitHub . We will use this topic to share all our plans for the upcoming release of Traefik 3.0. Comment below to discuss the overall direction of Traefik Proxy and share your overarching needs. :slight_smile: As always, we are still tracking individual feature requests in GitHub Issues , so if you wish to discuss the design, implementation, or other details of a particular issue, follow the link on the roadmap.

How to Read the Traefik Proxy Roadmap

The Traefik Proxy Roadmap is a kanban board divided into five lists ranging from nice-to-have to shipped:

  • Short term: We plan to complete this for the next release.
  • Mid-term: These are stretch goals for the next release. If they do not make it into the next release, they will become goals for the release after.
  • On hold: We have started working on these issues but encountered technical issues or prioritized them for a different release.
  • Nice-to-have: Things we have analyzed, we know we want to have, but it is not prioritized for the next 2 releases
  • Shipped: Feature fixes, and enhancements in GA

In addition to knowing where on our roadmap an issue lies. you can watch tags to learn more about the issue. There are tags identifying the type of issue it is (enhancement, feature fix), the status of the issue (exploring, ready for design, in progress, oh-hold and done), and tags telling you when it is targeted for release.

There is also a new tag, contributor/wanted, that helps identify issues that will have priority in the design and review stages should any community member choose to work on them. Should you decide to create a PR for these issues, the team will have a more rapid turnaround time for consultation and review.

If you are interested in contributing to Traefik Proxy, check out our contributing docs to get started.


What feature on the roadmap are you most excited about? Will having a public roadmap help you?

very interested in #6551, dynamic entrypoints configuration


Nice! We are exploring how to implement that rn. If you want to follow the issue specifically, you can do so on GitHub. How do you feel about the overall plan for Traefik Proxy 3.0?

If I can give you some advice, with Traefik 3 pay more attention to Spring Boot 2. I am a Spring Boot developer and I have not been able to use this proxy for my apps. I also recommend writing a page explaining how to transfer connections from www to non-www and vice versa.

@Milano2022 Spring Boot is not a problem for Traefik because Traefik manages containers.
Spring Boot is just an HTTP server inside a container.
Your problem is not related to this topic.