Konnect compatibility

Related Documentation
Incompatible with
on-prem

This reference explains which browsers, software versions, tools, and applications Konnect is compatible with.

Kong Gateway version compatibility

Konnect is compatible with the following versions of Kong Gateway:

Kong Gateway version Supported? Beginning with version End of support
3.10.x (LTS) 3.10.0.0 March 2028
3.9.x 3.9.0.0 Dec 2025
3.8.x 3.8.0.0 Oct 2025
3.7.x 3.7.0.0 Jun 2025
3.6.x 3.6.0.0 Feb 2025
3.5.x 3.5.0.0 Nov 2024
3.4.x (LTS) 3.4.0.0 Aug 2026
3.3.x 3.3.0.0 May 2024
3.2.x 3.2.1.0 Feb 2024
3.1.x 3.1.0.0 Dec 2023
3.0.x 3.0.0.0 Sep 2023
2.8.x (LTS) 2.8.0.0 Mar 2025
2.7.x 2.7.0.0 Feb 2023
2.6.x 2.6.0.0 Feb 2023
2.5.x 2.5.0.1 Aug 2022
2.4.x or earlier - -

Kong Mesh compatibility

To use Mesh Manager, you must also use a compatible version of Kong Mesh:

Kong Mesh version Supported? First supported patch
2.4.x or later 2.4.1
2.3.x or earlier -

decK version compatibility

Konnect requires decK v1.40.0 or above. Versions below this will see inconsistent deck gateway diff results and other potential issues.

Supported browsers

Konnect is compatible with the following browsers:

Browser Supported?
Chrome
Firefox
Edge
Safari
IE

Plugin compatibility

Most Kong Gateway plugins are compatible with Konnect. See the Kong Plugin Hub for all compatible plugins.

Considerations for Dedicated Cloud Gateways

There are some limitations for plugins with Dedicated Cloud Gateways:

  • Any plugins that depend on a local agent will not work with Dedicated Cloud Gateways.
  • Any plugins that depend on the Status API or on Admin API endpoints will not work.
  • Any plugins or functionality that depend on the AWS IAM AssumeRole must be configured differently. This includes Data Plane Resilience.

FAQs

The Kong Gateway Control Plane and its dependencies are fully managed by Konnect. As new versions of Kong Gateway are released, Konnect supports them as long as they are under our active support schedule.

An old configuration may still be 100% compatible with older Data Plane nodes and therefore not show any error messages in the Konnect UI. If there are compatibility issues detected when pushing the payload down to the Data Plane, then this will be reflected in the UI.

New features will not be available for use or consumption on incompatible Data Plane nodes. You will see new features available in the Konnect UI regardless of the Data Plane that is connected to the Control Plane in Konnect. However, when an update payload is pushed to an incompatible Data Plane, the update will be automatically rejected by the Data Plane.

This is managed by a version compatibility layer that checks the payload before the update gets sent to the Data Plane. If there are concerns with the payload, metadata is added to the node. That metadata is what will display incompatibility warnings or errors in the Konnect UI.

For example, let’s say a parameter is introduced with a new version of a plugin and is available in the Konnect UI. The Data Plane, however, is running an older version of Kong Gateway and doesn’t support the new parameter. If that parameter isn’t configured, or is assigned the default value, then no warning or incompatibility metadata will be applied to the node in Konnect, and no warnings or errors will appear.

Yes. All decK dumps, or YAML configurations, will continue to work in Konnect after they are synced.

There is no disruption at all if you choose not to upgrade your Data Plane nodes as long as the version of the Data Plane is under our Kong Gateway active support timeline.

Something wrong?

Help us make these docs great!

Kong Developer docs are open source. If you find these useful and want to make them better, contribute today!