I can't confirm this. I use traefik (+ Docker) for almost everything now. First thing I do with a new server is setup traefik as a systemd service. Everything runs smoothly and I didn't have any issues with the documentation. In fact, when I first tried it I was surprised because it just worked. It worked instantly. No googling, no weird errors, it just worked. Once you have a good understanding of how it works, it's just easy. I now have my default configuration which I can use almost everywhere. Also, automatic Let's Encrypt certificates are a big +

For use with vanilla docker and docker compose, traefik is absolutely convenient, though the issue with googling v1/v2 docs remains and will bite new user. But for use in kubernetes, I think sticking with nginx ingress and cert manager is better for new users as they basically provide similar fictionally (traefik is not marginally easier to use here) and there are myriads of resources on the internet available on how to use them.

If you're running other stuff in containers, I'm just curious why you'd choose to run Traefik outside a container?

Actually, it still runs inside a container using docker-compose. I just like it to set up my docker composes as a service

I spent waaaay too much time debugging configuration because I was running v2 but Google results gave me v1 options...maybe would have been a good idea to warn the user if they're using the old configuration format (afaik I didn't ever see a warning in logs).