Troubleshoot Data Plane Nodes
Out of sync data plane node
Occasionally, a Kong Gateway data plane node might get out of sync
with the Konnect control plane. If this happens, you will
see the status
Out of sync on the Data Plane Nodes page, meaning the control
plane can’t communicate with the node.
Troubleshoot the issue using the following methods:
Ensure the data plane node is running. If it’s not running, start it; if it
is running, restart it.
Check the sync status in the Gateway Manager.
Check the logs of the data plane node that’s appearing as
Out of sync. The default
directory for Kong Gateway logs is
If you find any of the following errors:
- Data plane node failed to connect to the control plane.
- Data plane node failed to ping the control plane.
- Data plane node failed to receive a ping response from the control plane.
You may have an issue on the host network where the node resides.
Diagnose and resolve the issue, then restart the node and check
the sync status in the Gateway Manager.
If the logs show a license issue, contact Kong Support.
If you are unable to resolve sync issues using the above methods, contact
If a Konnect feature isn’t working on your data plane node,
the version may be out of date.
Verify that your data plane node versions are up to date:
Open Gateway Manager, then open your control plane.
Select Data Plane Nodes from the side menu, then click the New Data Plane Node button.
Check the Kong Gateway version
in the code block. This is the version that the Konnect
control plane is running.
Return to the data plane nodes page.
Check the data plane node versions in the table. If you see
a node running an older version of Kong Gateway, your data plane node
may need upgrading.
If your version is up to date but the feature still isn’t working, contact
Kubernetes data plane node installation does not work
You followed the Kubernetes installation instructions in Gateway Manager
but your data plane node isn’t connecting.
Check your deployment logs for the error:
kubectl logs deployment/my-kong-kong -n kong
If you find any errors and need to update
values.yaml, make your changes,
save the file, then reapply the configuration by running the Helm
helm upgrade my-kong kong/kong -n kong \
Connect a data plane to Kong Konnect that is behind a non-trasparent forward proxy.
In situations where forward proxies are non-transparent, you can still connect the Kong Gateway data plane with the Kong Konnect control plane.
To do this, you need to configure each Kong Gateway data plane node to authenticate with the proxy server and allow traffic through.
For more information, see Control Plane and Data Plane Communication through a Forward Proxy in the Kong Gateway documentation.