Skip to content
Kong Logo | Kong Docs Logo
search
  • We're Hiring!
  • Docs
    • Kong Gateway
    • Kong Konnect
    • Kong Mesh
    • Plugin Hub
    • decK
    • Kubernetes Ingress Controller
    • Insomnia
    • Kuma

    • Docs contribution guidelines
  • Plugin Hub
  • Support
  • Community
  • Kong Academy
Get a Demo Start Free Trial
  • Kong Gateway
  • Kong Konnect
  • Kong Mesh
  • Plugin Hub
  • decK
  • Kubernetes Ingress Controller
  • Insomnia
  • Kuma

  • Docs contribution guidelines
  • 2.9.x (latest)
  • 2.8.x
  • 2.7.x
  • 2.6.x
  • 2.5.x
  • 2.4.x
  • 2.3.x
  • 2.2.x
  • 2.1.x
  • 2.0.x
  • 1.3.x
  • 1.2.x
  • 1.1.x
  • 1.0.x

github-edit-pageEdit this page

report-issueReport an issue

enterprise-switcher-iconSwitch to OSS

Kubernetes Ingress Controller
2.7.x
  • Home
  • Kubernetes Ingress Controller
  • References
  • Supported Kong Router Flavors
You are browsing documentation for an outdated version. See the latest documentation here.

Supported Kong Router Flavors

Kong Gateway (open-source and enterprise edition) includes an expression-based router in versions 3.0 and later. The router can be configured in the following modes:

  • traditional: uses the pre-3.0 router.
  • traditional_compatible: uses the expression based router, but the router configuration interface remains the same as traditional.
  • expressions: uses the expression-based router, and expressions must be provided in the router configuration interface.

The compatibilities of router flavors between different Kubernetes Ingress Controller versions and Kong Gateway are shown in the following table. Kubernetes Ingress Controller in versions 2.6.x and lower does not support Kong Gateway 3.0 and later, so the version of Kubernetes Ingress Controller begins at 2.7.x.

Kubernetes Ingress Controller 2.7.x 2.8.x 2.9.x
Kong 3.0.x traditional
Kong 3.0.x traditional_compatible (*) (*) (*)
Kong 3.0.x expressions
Kong 3.1.x traditional
Kong 3.1.x traditional_compatible (*) (*) (*)
Kong 3.1.x expressions

(*) Most use cases are supported. Regexes with a backslash (\) followed by a non-escaped character (for example, \j or \/) in matches of paths or headers may not be accepted when Kong Gateway 3.0 is configured to use the traditional_compatible router.

Thank you for your feedback.
Was this page useful?
  • Kong
    THE CLOUD CONNECTIVITY COMPANY

    Kong powers reliable digital connections across APIs, hybrid and multi-cloud environments.

    • Company
    • Customers
    • Events
    • Investors
    • Careers Hiring!
    • Partners
    • Press
    • Contact
  • Products
    • Kong Konnect
    • Kong Gateway
    • Kong Mesh
    • Get Started
    • Pricing
  • Resources
    • eBooks
    • Webinars
    • Briefs
    • Blog
    • API Gateway
    • Microservices
  • Open Source
    • Install Kong Gateway
    • Kong Community
    • Kubernetes Ingress
    • Kuma
    • Insomnia
  • Solutions
    • Decentralize
    • Secure & Govern
    • Create a Dev Platform
    • API Gateway
    • Kubernetes
    • Service Mesh
Star
  • Terms•Privacy
© Kong Inc. 2023