Upgrade went mostly without a problem (had set more than one Hostname for a service before, seems to not work anymore lol), and i have a pretty large configuration that has grown over the past two years.
What i noticed is that it is quite a bit faster. Also the dashboard shows a little more information than before and the logs have colours now.
You must log in or register to comment.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
Fewer Letters More Letters HTTP Hypertext Transfer Protocol, the Web k8s Kubernetes container management package nginx Popular HTTP server
2 acronyms in this thread; the most compressed thread commented on today has 11 acronyms.
[Thread #730 for this sub, first seen 1st May 2024, 08:45] [FAQ] [Full list] [Contact] [Source code]
I might give this a go. Have been using bog standard ingress nginx for my k8s but have wanted to try a gateway supporting ingress product for a while.
Thanks op.
He… give it a Go. ;)
Awesome! Just updated without issues, I only had to make one tiny change to my config.
That’s great for them and good on you for upgrading. After the upgrade from v1 to v2, I switched to caddy. Traefik was too much for me.
Damn, same, nuked Traefik when v2 broke the setup I spent hours trying to figure out. I don’t think the concepts are overwhelming, but something is profoundly wrong with their documentation habits. Now someone in the comments here is saying v3 changes the way paths are read with regex? Lol, fuck Traefik, never again.
Nothing wrong with that, Caddy is great!
I wish nginx had the concept of default header values for reverse proxies…
I mean, you can kind of do it with macros but man…
gui yet?
Yaml is better. But it has a dashboard.
Not necessarily just yaml — there are things yaml cannot do well, but even ignoring that, traefik can also use toml, or container labels — but rather, the entire concept of infrastructure as code is way better than GUIs. Infrastructure as code allows for much better linting, testing, and version controls thereby providing better stability and reproducibility.
If I’m not doing anything fancy and just use it for basic reverse proxy stuff for my docker containers, would I need to change stuff in the configs? Most of the stuff mentioned in the migration guide is about tls.caOptional stuff, which I don’t believe I use.
PathPrefix no longer being regex stood out
For real? Damn it that’s going to be painful.
Sounds like they actually changed it to Go language regex syntax instead of pearl syntax.
The documentation certainly makes it sounds like they just got rid of regex but this forum post seems to show otherwise.
https://community.traefik.io/t/pathprefix-regex/21819
I’m definitely in the wait for a month at least before attempting this upgrade camp…
All I had to do was remove one field to do with docker swarm which I don’t think I was using anyway.
Cool. I don’t have any swarm related config stuff.
Does it support Podman yet?
Found it out the hard way because I have automatic updates with watchtower… xD
Oof, that’s what killed my V1 setup lol
Definitely worth using specific versions on your docker images if you’re doing automatic updates.
traefik:mimolettefor example should keep you on 2.x versions while still getting patches and bug fixes.Yeah…I should be doing it but I am honestly too lazy to change my compose.
The only place I actually did it is my mongodb container bexause I know absolutely nothing about it.
At lwast I can rescue my traefik config :pI mean same, I say it’s worth using but I don’t do it either haha.
Everything is backed up every night, so if something breaks to the point of data loss I just fix it after.
I hope it went well :) i was completely ready to go back changing the image tag to v2 but didn’t need to.
Juat an error due to the swarmRefresh setting in the traefik.yml.
Because I am not running in swarm mode it threw an error.
Oh well. Life and learn ¯\_(ツ)_/¯
