A Data Plane node is a single instance of Kong Gateway that acts as a proxy and serves traffic.
In Konnect, Data Plane nodes are managed by Control Planes.
Control Planes manage and store configurations in Konnect, and they distribute those configurations to Data Planes nodes.
Data Plane nodes don’t manage their own configurations.
Konnect provides Data Plane node installation scripts for various platforms.
These Data Plane nodes are configured to run in your Konnect environment.
Alternatively, Konnect offers fully-managed Data Planes through Dedicated Cloud Gateways.
There’s no downtime when upgrading your Data Plane nodes. Additionally, you can pre-warm your cluster by specifying the number of requests per second so that the first requests don’t have to wait for the infrastructure to scale up.
Dedicated Cloud Gateways allows you to run a multi-cloud solution that allows you to standardize API operations across the board to reduce complexity and increase agility.
You need very rapid provisioning for experimentation and sandbox use cases.
Konnect supports using non-transparent forward proxies to connect your Kong Gateway Data Plane with the Konnect Control Plane. See the Forward proxy connections Kong Gateway documentation for more information.
Self-managed Data Plane nodes can be upgraded to a new Kong Gateway by initializing new nodes before decommissioning old ones.
This method ensures high availability, allowing the new node to start data processing prior to the removal of the old node.
Managed nodes are upgraded automatically after selecting the new version of Kong Gateway.
We recommend running one major version (2.x or 3.x) of a Data Plane node per Control Plane, unless you are in the middle of version upgrades to the Data Plane. Mixing versions may cause compatibility issues.
To upgrade a Data Plane node to a new version, follow these steps:
Using the control_plane_id, cloud_gateway_network_id, and the desired version, you can use the API to upgrade a Data Plane node:
Konnect performs a rolling upgrade of the fully-managed Data Plane nodes.
This is a zero downtime upgrade because Konnect synchronizes the Data Plane with load balancer registration and de-registration and gracefully terminates the old Data Plane nodes to reduce the impact on the ongoing traffic.
Open Gateway Manager, choose a Control Plane,
and provision a new Data Plane node through the Gateway Manager.
Make sure that your new Data Plane node appears in the list of nodes,
displays a Connected status, and that it was last seen Just Now.
Once the new Data Plane node is connected and functioning, disconnect
and shut down the nodes you are replacing.
You can’t shut down Data Plane nodes from within Gateway Manager. Old
nodes will also remain listed as Connected in Gateway Manager for a
few hours after they have been removed or shut down.
Test passing data through your new Data Plane node by accessing your proxy URL.
For example, with the hostname localhost and the route path /mock:
Data Plane certificates generated by Konnect expire every ten years. If you bring your own certificates, make sure to review the expiration date and associated metadata.
Renew your certificates to prevent any interruption in communication between
Konnect and any configured Data Plane nodes. The following happens if a certificate expires and isn’t replaced:
The Data Plane node stops receiving configuration updates from
the Control Plane.
The Data Plane node stops sending analytics and usage data to the Control Plane.
Each disconnected Data Plane node uses cached configuration to continue
proxying and routing traffic.
Depending on your setup, renewing certificates might mean bringing up a new Data
Plane, or generating new certificates and updating Data Plane nodes with the new
files.
The following parameters are the minimum settings required for a Data Plane node:
Parameter
Field in Konnect
Description and Value
role
n/a
The role of the node, in this case data_plane.
database
n/a
Specifies whether this node connects directly to a database. For a Data Plane, this setting is always off.
cluster_mtls
n/a
Enables mTLS on connections between the Control Plane and the Data Plane. In this case, set to "pki".
cluster_control_plane
n/a
Sets the address of the Konnect Control Plane. Must be in the format host:port, with port set to 443.
Example: Control plane endpoint in Konnect: https://example.cp.khcp.konghq.com Configuration value: example.cp.khcp.konghq.com:443
cluster_server_name
n/a
The SNI (Server Name Indication extension) to use for Data Plane connections to the Control Plane through TLS. When not set, Data Plane will use kong_clustering as the SNI.
cluster_telemetry_endpoint
n/a
The address that the Data Plane uses to send Analytics telemetry data to the Control Plane. Must be in the format host:port, with port set to 443.
Example: Telemetry endpoint in Konnect: https://example.tp.khcp.konghq.com Configuration value: example.tp.khcp.konghq.com:443
cluster_telemetry_server_name
n/a
The SNI (Server Name Indication extension) to use for Analytics telemetry data.
cluster_cert
Certificate
The certificate used for mTLS between CP/DP nodes.
cluster_cert_key
Private Key
The private key used for mTLS between CP/DP nodes.
lua_ssl_trusted_certificate
n/a
Either a comma-separated list of paths to certificate authority (CA) files in PEM format, or system. We recommend using the value system to let Konnect search for the default provided by each distribution.
konnect_mode
n/a
Set to on for any Data Plane node connected to Konnect.
vitals
n/a
Legacy Vitals analytics reporting mechanism. Set to off for all Kong Gateway versions >= 3.0. Set to on for Kong Gateway 2.8.x to collect Vitals data and send it to the Control Plane for Analytics dashboards and metrics.
Labels are commonly used for metadata information. Set anything that you need to identify your Data Plane nodes – deployment type, region, size, the team that the node belongs to, the purpose it serves, or any other identifiable information. For more information, review the Konnect labels documentation.
You can verify a Data Plane node by accessing a configured route through its proxy URL.
By default, Kong Gateway listens on port 8000, so a request to http://localhost:8000/{your-route} (or your custom hostname)
should return the expected response from your upstream service.