Traefik Reviews & Product Details - Page 3

With traefik we can keep the routing config in version control since it is attached to the service labels on the service container. We can keep the container and proxy settings in the same place so the service and be deployed and updated faster. Review collected by and hosted on G2.com.

It needs some templating system to avoid repeating config lines that are the same in many of our services. Review collected by and hosted on G2.com.

Lightweight micro-service service-discovery, support extensively for docker swarm, data center, Kubernetes.

1. Support Let's Encrypt automatic SSL certificate generation for all subdomains

2. Came along with load balancing. Also, we don't need to re-route traffic through Nginx as we do in Kubernetes if we open 80 and 443 ports

3. For all micro-services, add traefik configuration in the docker-compose file as service labels

4. Supports logging tools like jeager, prometheus, grafana

5. Cloud-native application proxy.

6. Less learning curve compared to Istio ingress

7. Excellent routing and traffic rules Review collected by and hosted on G2.com.

1. Does not support logging tools natively; needs to install and configure separately.

2. Performance is not better if service increases. Review collected by and hosted on G2.com.

I've had the joy of setting up traefik as reverse proxy for prometheus and grafana.

It's a great piece of software, written in Golang and open source. Let me explain what it makes so unique compared to Nginx/Apache/Haproxy.

traefik provides different way for configuration. You can feed it with YAML, JSON or TOML. There is no custom format, like in Nginx.

If you ever wrote a custom Ansible module for Nginx you know what I mean... with Traefik you can just pipe the YAML 1 to 1 to the traefik configuration. For configuration purposes Traefik provides an API and a nice dashboard, which helps for debugging. Traefik also provides natively prometheus metrics (something that nginx or apache do not) and I think that the router/middleware/service concept is pretty unique. Right now I am testing it in Kubernetes Environment and I am convinced so far, that I am going to use it as Ingress. Review collected by and hosted on G2.com.

While working on my reverse proxy setup for prometheus and grafana with traefik I had some difficulties with error debugging and the correct config file format. The configuration can be either in YAML, TOML or JSON and provides different elements like routers, middlewares and services. This concept is new for somebody who comes from the Nginx/Apache world and it might be difficult to fully understand it. During my setup I encountered a few situations, where I had the feeling that the debugging/logging output is not mature enough. I would like to have more verbose debugging. I am used to nginx, nginx can specify the exact error why something is not working. With traefik, however, this is far more difficult. Sometimes it's not clear why the middleware or why the service is not catching up the specific router. I wish there would be an explanation for the debugging output and maybe an in-depth guide for debugging and traefik troubleshooting. Review collected by and hosted on G2.com.

Traefik is very fast, understandable and tunable reverse-proxy and load-balancer. SSL with Let's Encrypt (auto-renew, one description for every entry points, security headers to have a hardened configuration) is a strong and good feature.

- Support is pro-active and development is fluent.

- Active community and helpful CM all over the world

- Nice and dynamic web UI

- Don't have to setup a strong architecture - Traefik just need to be in front of the web and that's it

- Auto discover is a fantastic functionality and Review collected by and hosted on G2.com.

Traefik deserves to be rigorous (yaml formatting). There are no real problem, you just have to be careful read the docs and be helped by the community. Review collected by and hosted on G2.com.

Traefik fits perfectly any container orquestrator (Swarm mode or Kubernetes) in a very simple deployment, replacing any reverse proxy (or ingress controller) you had before *AND* negotiating let's encrypt certificates for HTTPS easily. Traefik listens to any other deployment and reconfigures itself automagically.

I recommend Traefik to beginners and seasoned developers. It just works. Review collected by and hosted on G2.com.

Debugging is a bit harsh (default is very silent). Review collected by and hosted on G2.com.

Easy, feature-rich, and one tool which solves multiple customer use-cases. We really like the fact of how easy it is to deploy Traefik and get up and running with load-balancing, service discovery, and serving let's encrypt certificates. We use it for all of our customer demos and build a lot of services surrounding Traefik . Review collected by and hosted on G2.com.

Not enough time to try all the features.

- room for improvement in documentation Review collected by and hosted on G2.com.

The best part is its configuration is simple and it discover backend services on dynamic way without restart.

We have deployed this Product in MCE/Multi client environment to discover backend services. Review collected by and hosted on G2.com.

It's pretty complicated to migrate from traefik 1.x to 2.x version because not any proper document available on official site.

There is not any log rotation inbuilt feature available in traefik Review collected by and hosted on G2.com.

Super Easy to use,

Awesome documentation,

Integrated SSl solution provided by Let's Encrypt,

the most I like about this is it's routing mechanism without any additional configuration. Review collected by and hosted on G2.com.

As I am using traefic for last more than one year overall I am satisfied but just one thing I always think that they should provide documentation (a batter one) about how to configure as It takes too much time to figure out by .toml file which is all try and catch. Review collected by and hosted on G2.com.

Traefik is very easy to install regardless of which backend you're planning on using. Configuration is just as easy.

The Kubernetes integration is top-notch and makes it very easy to manage configuration, adding/removing routes, middleware, etc with standard tools. Review collected by and hosted on G2.com.

Traefik is still adding features. Support for UDP was only added recently and there are many other things still in the works.

That said, features do come quick and the developers & community are quick to respond. Review collected by and hosted on G2.com.