Kong Konnect
Kong Konnect is a powerful, cloud-native API management solution designed to simplify and secure the deployment of APIs and microservices. By integrating Kong Konnect with Traceable, organizations can enhance API security, gain end-to-end visibility, leverage advanced threat detection, and optimize API performance. Integrating Kong Konnect with Traceable enhances API security, providing traffic monitoring to detect threats like malicious calls and data exfiltration. It also offers end-to-end visibility into API interactions across environments and advanced machine-learning-based threat detection to identify sophisticated threats proactively.
Before you begin
Make a note of the following points before proceeding with deployment steps:
Access to Kong Konnect and Kong Gateway Deployment: Ensure Kong Konnect and Kong Gateway are set up.
Download Tools: You’ll need
curlandluarocks.Traceable Platform agent: Ensure the Traceable Platform agent (TPA) is installed. For more information, see Installation.
Traceable API Access: Ensure the Traceable Platform Agent (TPA) is reachable from Kong Gateway.
Namespace Details: If using Kubernetes, confirm the Kong namespace.
Deployment steps
Step 1: Download and Unpack the Traceable Kong Plugin
Download the plugin from LuaRocks:
curl -LO https://luarocks.org/manifests/traceableai/kong-plugin-traceable-2.1.2-1.src.rockUnpack the downloaded plugin:
luarocks unpack kong-plugin-traceable-2.1.2-1.src.rock
Step 2: Upload the Plugin Schema to Kong Konnect
Navigate in Kong Konnect:
Gateway Manager → [Select a Gateway] → Plugins → New Plugin

Select Custom Plugins tab → Create under Custom Plugin.

Upload the
schema.luafile from the Traceable plugin → Save.
To enable and configure the plugin:
Go back to Plugins → Enable on the Traceable plugin.

Configure the plugin options on the configuration page using the following settings:
Global vs Scoped
Global will apply to all services on the gateway, while Scoped allows granular control over which APIs send traffic to the Traceable plugin.
Allow on Failure
Only used in sync mode; will block a request if communication to TPA fails.
Buffer Request Body
Only used in async mode, to buffer the request body for async export.
Ext Cap Endpoint
TPA Host, which must be reachable from the Kong gateway.
Mode
sync: Supports inline blocking; requires TME on the same Kong host.
async: Does not support blocking and is asynchronous.
Timeout
Connection timeout from Kong plugin to TPA, specified in milliseconds.
Service Name
Name that will appear in the Traceable UI.

Step 3: Add the Plugin to Kong Gateway Deployment
Option 1 — VM deployment
If you are running Kong on virtual machines (VMs), you can install the plugin using the following LuaRocks command:
Option 2 — Custom Docker Images
If using custom Kong Docker images, you can copy the kong plugin sound code and set the KONG_PLUGINS environment variable as shown below:
Option 3 — Official Docker Images (Volume Mount)
If you are using the official Kong Docker images and do not build custom Kong images, you can add the Traceable plugin by attaching a volume and setting the required environment variables. Use the following configuration:
Option 4 — Kubernetes with Helm
If you are deploying Kong in Kubernetes with Helm, you can deploy the Traceable plugin source code as a ConfigMap.
Download the Plugin:
Unpack the Plugin:
Create the ConfigMap Replace
-n kongwith your specific namespace if different:Update the Helm
values.yamlfile for Kong:
Option 5 — Kubernetes without Helm
If you are deploying Kong in Kubernetes without Helm, you can apply a strategic deployment patch to add the plugin volume. Follow these steps:
Download the Plugin:
Unpack the Plugin:
Create the ConfigMap Replace
-n kongwith your specific namespace if different:Create a Deployment Patch File: Save the following YAML content in a file named
kong-traceable-patch.yml. Replace<replace with your metadata name>and<replace with your namespace>with your actual deployment name and namespace:Apply the Deployment Patch: Apply the patch to your Kong deployment using the following command. Make sure to replace
<replace with deployment name>with the actual name of your Kong deployment:
Last updated
Was this helpful?