funny and sad how ingress-nginx loses all users by going into maintenance mode, and once we switched we dont care about their new project
Managed Nginx is standard for AKS. I wouldn’t say it’s gone.
Traefik's 10-year anniversary
91–100 of 154 posts
Re: Traefik's 10-year anniversary
#92I use Traefik for local development on daily basis, where I have to run double digit https services. It works, but it was a pain to set up. The documentation sucks ** and the config is confusing AF. I would never recommend this to anyone. If i will have to reinstall my computer one day, Traefik will not be welcomed back.
I use caddy similarly, but it's a pretty straight forward setup.
As a self-hosting noob, I never got traefik to work properly, then caddy just worked and has been working since.
Re: Traefik's 10-year anniversary
#93I use and appreciate both Traefik and Caddy. I like that Traefik includes TLS termination, whereas the equivalent functionality with Caddy requires compiling a separate module with xcaddy.
I'm pretty sure that's how I'm already using Caddy, and I didn't compile anything separate. Maybe it's packaged automatically as part of the Caddy Docker image?
Re: Traefik's 10-year anniversary
#94Earlier quoted context omitted.
With JWTs I don't do anything at the proxy beyond "This is a protected route. Is there a JWT? Is it valid? No to either? 403." This is one of the primary use cases for JWTs and it takes a majority of the load off of my application servers. The route is open to the public for authenticated and authorized users. You wouldn't use a VPN here.
That's really just added work, IMO, and likely room for security misconfiguration between backend and proxy. You should still be validating and everything on the application server to inspect identity and possibly attributes like roles, so in the cases where you have invalid tokens you do the work once, just in the proxy instead of the backend, and with valid tokens you will do the signature validation work twice.
If you're concerned about misconfigurations, just verify/validate everything in tests.
Re: Traefik's 10-year anniversary
#95Anyone know of a Traefik alternative but in Rust? I'm looking to oxidize a lot of my stack so just curious.
Looking for a Rust-based alternative to a battle-tested industry-standard tool written in a memory-safe language that can get about 75-90% of the speed of Rust is kind of pointless outside embedded context.
Re: Traefik's 10-year anniversary
#96I use Traefik for local development on daily basis, where I have to run double digit https services. It works, but it was a pain to set up. The documentation sucks ** and the config is confusing AF. I would never recommend this to anyone. If i will have to reinstall my computer one day, Traefik will not be welcomed back.
OMG yes. I want to like Traefik, but the thought having to set it up again is not something i look forward to. Why cant it just work out of the box?
Caddy is probably my new favorite. It works out of the box, its super low resource, handles a ton of traffic, and the docs are decent.
Re: Traefik's 10-year anniversary
#97I use Traefik for local development on daily basis, where I have to run double digit https services. It works, but it was a pain to set up. The documentation sucks ** and the config is confusing AF. I would never recommend this to anyone. If i will have to reinstall my computer one day, Traefik will not be welcomed back.
I really like how it can be easily configured from Docker labels (from Portainer for example), or from your big production Consul cluster alike. But yeah, the docs need a lot of work, it’s difficult to figure out the format many times, it lacks examples, and things that need to be enabled together have their docs at different places.
Re: Traefik's 10-year anniversary
#98Earlier quoted context omitted.
Caddy is a webserver like Apache or nginx. Integration with Docker is a higher-level layer. There’s caddy-docker-proxy but I haven’t tried it.
Traefik is also a web server like Apache or Nginx and it does integrate with Docker. I thought that feature was like the entire reason to use Trafik, so I guess I just find the comparison a bit strange.
Traefik is a proxy first
Re: Traefik's 10-year anniversary
#99With 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…
Yea, envoy is the premier open source (not open core+ paid features) proxy right now in my opinion. Modern, well supported, big community, reliable. If I was making a bet long term I would be looking at envoy and not some open core crap where they can rug pull you at any moment.
Traefik is proper OSS tho, not Open Core
Re: Traefik's 10-year anniversary
#100Earlier quoted context omitted.
I agree “standard” is not the right word here. Traefik is very popular in self hosting community, probably the most popular proxy in my experience, followed by NPM (nginx proxy manager) and Caddy as distant third.
Is there a way to use Envoy with common self-hosting software stacks like Docker Swarm?
Isn’t Docker Swarm dead?