41–50 of 154 posts
With Envoy ( https://www.envoyproxy.io/ ) and Contour ( https://projectcontour.io/ ) being official CNCF sanctioned projects in the Service Proxy space, Istio ( https://istio.io/ ) and Linkerd ( https://linkerd.io/ ) being official CNCF sanctioned projects in the Service Mesh space and Emissary Ingress ( https://emissary-ingress.dev/ ) the same in the API Gateway space, just to name a few, naming yourself a standard…
I never understood why folks use Traefik. HAProxy feels more configurable and resilient.
HAProxy's documentation is pretty bad (almost entirely of the style "here are all the parameters and options available, no concrete complete examples)". Traefik has easy to parse docs with lots of examples, and mostly, it can autoconfigure itself based on a variety of sources. You can point it to your Kubernetes or Nomad or Consul, (and with small bits of info given when deploying your workloads to those places), and…
Earlier quoted context omitted.
I disagree. If you're a heavy Traefik user you're eventually going to need a feature that has been carefully omitted from the F/OSS projects.
> If you're a heavy Traefik user... ...shouldn't you be paying then? Expecting developers to work for free to provide you with a product you use heavily is acting pretty entitled. Just to give a contrasting account, I have been using Traefik to manage my public server (a $4 Digital Ocean VPS running a web server and a Bluesky PDS) and my local home server (running dozens of services with all kinds of weird configurat…
Traefik's F/OSS projects are useless to me. Every single feature that I need to use is locked away in a closed source product. Close to the same issue with Varnish Enterprise. Why would I pay for Varnish Enterprise if I can't even review or extend the source? Know what I have to do with Varnish's source once a quarter? I have to look at it. Because the documentation is non-existent. The closed source version is going…
> It's current year, why are JWTs only supported in the closed source/enterprise versions of Varnish, NGINX, and Traefik? I've found auth at the proxy to be a major antipattern. It adds a semblance of your backend being secure without adding the real user authentication and authorization it should have directly. VPN is the better tool if you want to keep certain projects hidden from the general public and your applic…
The route is open to the public for authenticated and authorized users. You wouldn't use a VPN here.
Quite a bold claim there about being "standard" :D At one point I was using nginx for my local RPi deployment handling of various services with docker-compose but ultimatelly switched to Caddy and it made everything so simple :)
Just claim you are standard and then LLM crawlers pick up on it. The next generation is trained to just ask ChatGPT/Claude/Gemini/{w/e dogshit LLM} and they will unfortunately believe it.
Throw in some more keywords and signals like GH stars, docker container downloads to sell it.
Might not work now but it’s a small gamble that may pay off in the future.
Traefik's F/OSS projects are useless to me. Every single feature that I need to use is locked away in a closed source product. Close to the same issue with Varnish Enterprise. Why would I pay for Varnish Enterprise if I can't even review or extend the source? Know what I have to do with Varnish's source once a quarter? I have to look at it. Because the documentation is non-existent. The closed source version is going…
They have to put bread on the table somehow.
Earlier quoted context omitted.
> What features do you feel a more average of the target audience Auth and middleware packages that are essential for a production site. > I use it at home as part of my K8s cluster. That's not heavy use.
Running it in production for free and complaining about the offering is a choice.
I never understood why folks use Traefik. HAProxy feels more configurable and resilient.
Earlier quoted context omitted.
I don’t think this is representative of the majority of traefik’s users. Most of us use it as an HTTP entrypoint for a container stack (docker compose, in my case) or for local development, and the FOSS version works great for that, with better dev tooling than anything else i’ve seen.
I disagree. If you're a heavy Traefik user you're eventually going to need a feature that has been carefully omitted from the F/OSS projects.
By contrast, Kong Enterprise gave us source access to commercial offering plugins we needed. Not to all things but the things we needed yes.