Traefik Proxy

What do you like best about the product?

The community isn’t a one-size-fits-all pony trick. It keeps you sharp and pushes you to think in terms of possibilities.

What do you dislike about the product?

I HATE the fact from the start de logging (debugging) output cannot be enabled on the channels of your choice and not pick 1.

What problems is the product solving and how is that benefiting you?

Reverse proxy LAN / WAN (CF), inconsistencies DNS01 cert validation, multi domain lan DNS management. Its challenging, but interesting

What do you like best about the product?

The simplicity: It works extremely well as an on-premise reverse proxy implementation for teams that are adopting containerization and modern development tooling like Docker. The documentation is well structured, easy to follow, and makes it trivial to find what you're looking for.

What do you dislike about the product?

I haven't encountered anything that has made me dislike traefik.

What problems is the product solving and how is that benefiting you?

The organisation uses primarily Docker swarms for container orchestration and Traefik makes it very easy to add SSL to any services within Docker swarms. It's so easy to setup and requires minimal maintenance to keep going.

What do you like best about the product?

Flexibility on defining configuration in various different environments. The native support for docker using label is very smart

What do you dislike about the product?

Navigating through docs to find examples is a little bit challenging because they must provide examples for every single environment (docker, kubernetes, or even file). But once you get it, it is convenient

What problems is the product solving and how is that benefiting you?

Homelab setup with a lot of docker compose. Native support for docker with labels as config is very fitting to my use case

What do you like best about the product?

Super easy to integrate with docker and very simple to configure and extend 👌

What do you dislike about the product?

Initially a bit reading work to do but checking the documentation makes sense in any case, so it's not something I dislike but rather the work I expect to put into. Still not that complicated😉

What problems is the product solving and how is that benefiting you?

At work and privately we are using Traefik to route our docker environment together. And it is a perfect fit for that👌

What do you like best about the product?

There are several things that I really like about traefik. Firstly, I like the organization it gives me in my hosting setup. I run several websites from the same host, and managing a dockerized traefik hosting setup is immensely easier than managing multiple sites on a conventional web server like apache or nginx. It's routing tools allow me to set sites up and take them down with ease, and I like that the configuration can be defined in docker-compose. The automatic ssl feature is also incredibly nice once you figure it out. I also like the web dashboard.

What do you dislike about the product?

Traefik has a steep learning curve. If you are a newcomer to products like traefik, it will take some time to build an understanding of what it is, how it works, and what the different terms mean. I had to put in many hours to really understand what was going on with the automatic ssl certificate resolvers in particular. In particular, there are a few "magic settings" with automatic ssl that make it work, but I still don't understand exactly why.

What problems is the product solving and how is that benefiting you?

Traefik allows me to host multiple web servers on a single host by routing requests to different web server docker containers based on domain name. This means that I can have multiple websites that use the default http/https ports on my host. The ability to use docker-compose to set up my sites also makes them incredibly easy to spin up, tear down, and manage. Finally, the SSL certificate resolvers are incredibly useful for making all my sites communicate over https by default.

What do you like best about the product?

Traefik is an exceptional choice for modern cloud-native environments, offering extensive configuration options that make it incredibly versatile and powerful. Whether you're deploying microservices, managing complex traffic routing, or securing your infrastructure, Traefik can handle it with ease. The level of customization available through its configuration is one of its standout features. You can fine-tune every aspect of your setup, from load balancing algorithms and request retries to SSL termination and advanced routing rules.

The comprehensive documentation provided by Traefik is another major advantage. It’s well-organized, detailed, and covers virtually every possible use case. Whether you’re just getting started or diving deep into complex scenarios, the documentation is a reliable resource. It walks you through configurations, best practices, and even troubleshooting, ensuring that you can make the most out of Traefik's extensive capabilities.

Moreover, Traefik is incredibly flexible and can be used in almost any environment or use case. It supports a wide range of orchestrators like Kubernetes, Docker, and more. This versatility allows it to fit seamlessly into various infrastructures, from small-scale setups to large, complex systems. Whether you need to manage traffic for a single application or a sprawling microservices architecture, Traefik is equipped to meet the challenge.

Overall, Traefik’s extensive configuration options, robust documentation, and wide applicability make it an indispensable tool for anyone looking to efficiently manage their network traffic in a scalable and secure way.

What do you dislike about the product?

While Traefik is highly versatile and powerful, its extensive configuration options can be overwhelming for first-time users. The sheer number of settings and possibilities might make it challenging to get started, especially if you're new to the concepts of reverse proxies, load balancing, or modern cloud-native architectures. Navigating through the various configuration methods—whether via YAML files, labels in Docker, or dynamic configurations—can be complex, requiring a solid understanding of the underlying principles.

However, once you get past the initial learning curve, the flexibility and control that Traefik offers are unmatched. The comprehensive documentation helps mitigate this complexity, guiding you through the setup process and helping you understand how to tailor Traefik to your specific needs. With time and experience, you'll likely find that the initial complexity is a small price to pay for the robust and customizable infrastructure that Traefik enables.

What problems is the product solving and how is that benefiting you?

Traefik excels at solving the problem of managing multiple ingress routes, particularly when it comes to certificate management. In environments where multiple services require secure access, handling SSL certificates can quickly become a complex and time-consuming task. Traefik streamlines this process by automating certificate management, including the generation, renewal, and deployment of SSL/TLS certificates.

What do you like best about the product?

Traefik stands out for its simplicity and powerful features. The use of routers, middleware, and services makes managing applications straightforward. One of the biggest advantages is the seamless integration of HTTPS with real signed certificates, which simplifies the security aspect across multiple applications. What I love most about Traefik is its dynamic discovery of new services. Whether using Docker, files, or other methods, just adding a new file or creating a container with the right labels automatically configures the router/service. This flexibility and speed in service management are unparalleled.

What do you dislike about the product?

The learning curve can be challenging for newcomers. It’s not difficult to reach a point where you feel comfortable, but until you do, it might feel overwhelming. However, once you get the hang of it, Traefik’s benefits far outweigh this initial hurdle.

What problems is the product solving and how is that benefiting you?

Traefik solves the problem of efficiently managing and routing traffic to multiple services in a dynamic environment. It simplifies the process of setting up and maintaining secure, well-organized application gateways, especially in environments where services are constantly changing, such as with Docker containers.

For me, Traefik’s ability to dynamically discover and configure new services is a game-changer. It eliminates the need for manual configuration every time a new service is added, which not only saves time but also reduces the risk of configuration errors. Additionally, its built-in support for HTTPS with real signed certificates ensures that all my applications are secure without extra hassle.

What do you like best about the product?

Traefik makes setting up reverse proxies and load balancers super-easy to implement when using containerized infrastructure. If you're running Docker containers or Kubernetes clusters, the out-of-the-box integration is really solid and makes it so easy to configure once you know how it works. I use Traefik for both small homelabs and larger organizations, and it can fit well into these different environments.

One of the best parts about Traefik is that it includes a ton of functionality baked into the service, like automatic SSL certificate generation for your web applications and middleware to manipulate incoming requests. You don't need to deal with plugins or additional software nor modify your applications, and configuring them is straightforward. Having a lot of these systems in a single place helps managing things a breeze. The included dashboard is also useful to see your complete setup.

What do you dislike about the product?

The initial learning curve can feel a bit steep as you get used to learning how to use Docker labels to configure Traefik or setting up a new ingress controller on Kubernetes. Documentation is good enough and comprehensive, but in the beginning it can be difficult to navigate for those new to Traefik, mostly because of all the functionality it includes.

Debugging issues can be a bit of a challenge at times, especially when involving more complex setups of routers and middleware. With all the points where something can go wrong and sometimes-unclear error logs, fixing problems when they arise can take quite some time to deal with.

What problems is the product solving and how is that benefiting you?

Traefik has helped me deal with a few things in my infrastructure:

- Managing routing rules for microservices to allow me to handle where my incoming traffic goes.
- Simple service discovery for new Docker containers which lets me add new microservices without needing additional configuration.
- Automatic SSL certificate generation so I don't have to worry about renewing them.
- Easy-to-add middleware options for rate limiting and basic authentication when needed.

What do you like best about the product?

I'm very pleased with how well Traefik follows the Kubernetes Gateway API. They have added an elegant extension point to host their great middleware feature. I believe that this approach can make it to the standard.
The move to WebAssembly for the middleware is strategically smart because it will widen the community and makes middleware execution more efficient. But it is also key in standardising middleware.

What do you dislike about the product?

I haven't come across any issues yet. It just works.

What problems is the product solving and how is that benefiting you?

The Traefik Proxy is the external entry point for our Kubernetes clusters on AWS EKS. All external traffic to the services is routed through and balanced by Traefik Proxy. In combination with the external-dns and cert-manager projects, it also carries and terminates the public domain names we expose. Lastly, we have created an OpenID Connect middleware, that intercepts all requests and drives the authentication of the end-user.

What do you like best about the product?

I chose Traefik for work at first, building a Docker Swarm serviced by Traefik for ingress to the many websites therein. I could very easily template my compose files with the appropriate configuration, and required nearly zero maintenance on the Traefik stack for the life of the swarm.

When I refreshed my homelab, I chose Traefik for the same reasons, and I've been running it ever since. Not only was moving from v1 to v2 super easy, it's been even more stable and hands-off.

What do you dislike about the product?

There's a fair bit to initially know and understand for proper setup, but documentation is pretty excellent.

What problems is the product solving and how is that benefiting you?

Easy container routing for webhosts and other similar concerns.