We are looking at Kong LTS upgrade (2.8 to 3.4) for our systems and have been going though the LTS upgrade doc and understand all of the required changes needed. I am using the default “traditional_compat” router mode.
I started testing some of our Config and found that Kong logged the following error when creating/updating a route that used “v1” path_handling.
025-07-22 13:51:49 2025/07/22 05:51:49 [warn] 1294#0: *1196 [kong] routes.lua:117 path_handling='v1' is deprecated and will not work under 'traditional_compatible' router_flavor, please use path_handling='v0' instead (deprecated after 3.0), client: 172.18.0.1, server: kong_admin, request: "PUT /routes/e98e8947-dd02-4e30-b8fa-7519292b098f HTTP/1.1", host: "localhost:8001"
The Routes - Kong Gateway | Kong Docs documentation shows both v0 and v1 are supported in path_handling with a warning box indicating that v1 is not supported in the expressions router, which in Expressions router - Kong Gateway | Kong Docs is used when router_flavor = expressions. It does not mention anything about v1 not compatible with router_flavor = traditional_compat.
There is also no mention of path_handling as a breaking change in the Kong Gateway 2.8 to 3.4 LTS upgrade - Kong Gateway | Kong Docs or the Kong Gateway breaking changes - Kong Gateway | Kong Docs.
It seems that Kong is reverting to v0 handling when i try and test the route. I also noticed in Decks new LTS convert command it has config linting that prints a warning when it find v1.
So is v1 supported in traditional_compat mode or should i change any of our configs that use v1 to v0 and fix any paths due to the change.