Traefik Reviews

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.

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

The organisation uses primaririly 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 maintainance to keep going.

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

Initally 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😉

At work and privately we are using Traefik to route our docker environment together.

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.

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.

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.

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.

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.

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.

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.

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.

Ease of Integration: Would be as easy as changing the ingressClassName

Ease of Implementation: A comprehensive Helm Chart is provided

Traefik is a modern edge router and reverse proxy, widely praised for its flexibility and ease of use. Here are some advantages of Traefik summarized from our project:

1. Automatic Service Discovery and Configuration: Traefik can automatically discover services and generate routing rules based on configuration. This greatly simplifies service management in a microservices architecture.

2. Multi-backend Support: Traefik supports multiple backends, including Docker, Kubernetes, Mesos, etc., and can be easily integrated into different environments.

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.

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

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.

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.

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

Traefik is a very powerful reverse proxy solution I'm currently using to simplify the access to a hundred services in my homelab.

There's tons of functionality, making it a highly configurable reverse proxy, with built-in support for Let's Encrypt.

There are a number of different ways to configure Traefik, and I particularly like the Docker integration, which lets you configure Traefik with Docker labels, very useful when you want to quickly deploy a new service and integrate it into your architecture.

As Traefik is a highly flexible solution, it's also rather complex to understand at first. There's a bit of a learning curve, but you can get by with the help of documentation and resources available on the Internet.