Manage all your services
Organize developers and permissions
Empower your developers
Autonomously identify issues
Native Kubernetes Ingress Controller
Instantly implement policies
Monitor your Kong Enterprise
API Design and Testing
Ingress and CRDs
Kong Gateway and Enterprise features
Accelerate your journey into microservices
Empower teams to provide security, governance and
Rapidly design, publish and consume APIs and services
Take control of your microservices with the world’s most
popular API gateway
Own your Kubernetes cluster by using Kong as an Ingress
Build, secure and observe your modern Service Mesh
All features of decK work with both Kong Gateway and Kong Enterprise.
For Kong Enterprise, decK provides a few additional features leveraging the
power of enterprise features.
decK is compatible with Kong Enterprise 0.35 and above.
decK manages only the core proxy entities in Kong Enterprise. It doesn’t
manage enterprise-only entities such as admins, RBAC permissions, RBAC roles,
or any entities related to Developer Portal.
You should have authentication and RBAC configured for Kong’s Admin API.
You can supply the RBAC token to decK so that decK can authenticate itself
against the Admin API:
--headers "kong-admin-token:$(cat token.txt)"
It is advised that you do not use an RBAC token with super admin privileges
with decK, and always scope down the exact permissions you need to give
decK is workspace-aware, meaning it can interact with multiple workspaces.
To export the configuration of a specific workspace, use the --workspace flag:
deck dump --workspace my-workspace
If you do not specify a flag, the configuration of the default workspace will
You can export the configurations of all workspaces in Kong Enterprise with
the --all-workspaces flag:
deck dump --all-workspaces
This creates one configuration file per workspace.
If a workspace is not present, decK will error out.
You should ensure that a workspace already exists before using decK.
diff and sync commands work with workspaces, and the workspace to sync
to is determined via the _workspace property inside the state file.
It is recommended to manage one workspace at a time and not clump
configurations of all the workspaces at the same time.
Same as the dump command, you can use -workspace to reset configuration of a
specific workspace, or use --all-workspaces to reset configuration of all
workspaces in Kong.
Please note that decK doesn’t delete the workspace itself but deletes the
entire configuration inside the workspace.