decK can manage entity configuration for Kong Gateway, including all core proxy entities.
It does not manage Kong Gateway configuration parameters in kong.conf, or content and configuration for the Dev Portal.
decK supports the following entities:
| Entity | Managed by decK? |
|---|---|
| Services | Supported |
| Routes | Supported |
| Consumers | Supported |
| Plugins | Supported |
| Certificates | Supported |
| CA Certificates | Supported |
| SNIs | Supported |
| Upstreams | Supported |
| Targets | Supported |
| Vaults | Supported |
| Keys and Key Sets v1.48+ | Supported |
| Licenses | Not supported |
| Workspaces 1 | Supported |
| RBAC roles and endpoint permissions | Supported |
| RBAC groups and admins | Not supported |
| Developers | Not supported |
| Consumer Groups | Supported |
| Event hooks | Not supported |
| Keyring and data encryption | Not supported |
| Partials | Supported |
[1]: decK can create workspaces and manage entities in a given workspace. However, decK can’t delete workspaces, and it can’t update multiple workspaces simultaneously. See Manage multiple workspaces for more information.
While decK can manage a majority of Kong Gateway’s configuration, we recommend additional arrangements for deployment, backup, and restoring unmanaged entities for a more comprehensive approach.