Open
Conversation
Elson9
approved these changes
Mar 11, 2026
Contributor
Elson9
left a comment
There was a problem hiding this comment.
Looks good, added a couple tests.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
The
gwa-apiprovisions gateway configuration on Kong using Kong's Admin API and thedeckCLI. With the introduction of the Secure Data Exchange, there could be any number of SDX Edge Servers running. Three changes are being made to support SDX:Due to the way Edge Servers are deployed, there is no need to use the Kube-API to provision additional resources to setup routes, so this feature needs to be disabled when the data plane is an Edge Server.
The Kong Control Plane for the API Gateway has sensitive information, which is OK when the same team that runs the data planes also runs the control planes. But with SDX, the Edge Servers will be operated by different organizations. For this reason, a new Kong Control Plane will be used for distributing configuration to Edge Servers. Provisioning new routing policies will ensure that no sensitive information (private keys, passwords, etc) will be part of the configuration.
Open up the ability to configure
key_setsandkeysso that teams are able to register public keys that can be used to verify tokens that are signed by their own private keysTypes of changes
Checklist