Router Flavor

Kong Ingress Controller supports the traditional, traditional_compatible and expressions Kong Gateway routers. Set gateway.env.router_flavor in your values.yaml when installing with Helm to configure the router used.

When using Gateway API resources we recommend using the expressions router because it supports advanced features such as query string matching, which the traditional and traditional_compatible routers do not support

Kong Ingress Controller 3.0 changed the default router_flavor from traditional_compatible to expressions. For DB-less deployments you should not notice any difference in behaviour. For DB-backed deployments, set gateway.env.router_flavor: traditional_compatible in your Helm values file.