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
One of the most important features of decK is reverse sync, whereby decK can
detect entities that are present in Kong’s database but are not part of the
This feature increases the complexity of the project as the code needs to
perform a sync in both directions: from the state file to Kong, and from Kong
to the state file.
An export or reset of entities is fairly easy to implement.
decK loads all the entities from Kong into memory and then serializes
it into a YAML or JSON file. For reset, it instead performs DELETE queries
on all the entities.
The diff of configuration is performed using the following algorithm:
Certain filters like select-tag or Kong Enterprise workspace might be applied
to the above algorithm based on the inputs given to decK.
Based on the above algorithm, one can see how decK can require a large amount
of memory and network I/O. While this is true, a few optimizations have
been incorporated to ensure good performance:
decK is written in Go because: