With the release of Kong Gateway 3.0, Route paths that use regular expressions are no longer automatically detected.
For Kong Gateway to parse a path that contains a regular expression, the path must be prefixed with a ~
.
For example, in 2.x, a Route path that was expressed like this:
/status/\d+
Would need to be rewritten in the new 3.0 format:
~/status/\d+
If you migrated your Kong Gateway database from 2.8.x to 3.0, the ~
prefix is automatically added to the Route paths in the database.
This causes configuration drift between the formats of the Routes that exist in the database and the Routes in your configuration file.
Before using your state files to update the database, convert them into the 3.0 format using deck convert
.
Important: Don’t use
deck sync
with Kong Gateway 3.x before converting paths into the 3.0 format. This will break all regex routing in 3.x.