decK manages 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.
| Entity | Managed by decK? |
|---|---|
| Services | |
| Routes | |
| Consumers | |
| Plugins | |
| Certificates | |
| CA Certificates | |
| SNIs | |
| Upstreams | |
| Targets | |
| Vaults | |
| Keys and Key Sets | |
| Licenses | |
| Workspaces 1 | |
| RBAC roles and endpoint permissions | |
| RBAC groups and admins | |
| Developers | |
| Consumer Groups | |
| Event hooks | |
| Keyring and data encryption | |
| Partials |
[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.