(Legacy) Deployment Overview
This documentation is for the legacy Konnect environment at
konnect.konghq.com. For the
cloud.konghq.com environment, see the
current Konnect documentation.
The Kong Konnect platform provides a cloud control plane (CP),
which manages all service configurations. It propagates those configurations to
all runtime nodes, which use in-memory storage. These nodes can be installed
anywhere, on-premise or in the cloud.
Runtime nodes, acting as data planes, listen for traffic on the proxy port 443
by default. The Konnect data plane evaluates
incoming client API requests and routes them to the appropriate backend APIs.
While routing requests and providing responses, policies can be applied with
plugins as necessary.
For example, before routing a request, the client might be required to
authenticate. This delivers several benefits, including:
- The Service doesn’t need its own authentication logic since the data plane is
- The Service only receives valid requests and therefore cycles are not wasted
processing invalid requests.
- All requests are logged for central visibility of traffic.
Note: Currently, the only supported runtime type in
Konnect Cloud is a Kong Gateway
||First supported patch version
|Kong Gateway 2.7.x
|Kong Gateway 2.6.x
|Kong Gateway 2.5.x
|Kong Gateway 2.4.x
|Kong Gateway 2.3.x
|Kong Gateway 2.2.x or earlier