If you've not heard of decK (our declarative configuration and drift detection tool for Kong Gateway) before, now's a great time to get hands-on with it as we've just shipped decK v1.7.0 with a whole host of new goodies. Oh, and it's all open source as usual.
v1.7.0 adds lots of Konnect-related functionality that I'm really excited about, starting with the new deck convert command. deck convert allows you to take a declarative configuration file from an on-premises Kong Gateway (both OSS and Enterprise) and convert your configuration into a format that Konnect can use:
deck convert --from kong-gateway --to konnect --input-file kong.yaml --output-file konnect.yamlDid you know that Konnect is available in regions all over the world? If you happen to use this functionality, you'll be glad to know that v1.7.0 contains a –konnect-addr flag which allows you to use decK with any Konnect instance.
Finally, this release adds support for service documents and OpenAPI specs when running deck konnect dump. This allows you to manage your documentation declaratively as well as your service configuration, making it even easier to practice APIOps with Kong.
There are some quality-of-life changes like default HTTP request timeouts or a better sort order for entities when running deck dump (thanks to @mmorel-35 for the issue and subsequent pull request).
If you've been looking for a way to provide sensitive information in your state files, we've got you covered. This change allows you to define parameters in your environment and access them in your declarative configuration using the env helper e.g.:
consumers:
- keyauth_credentials:
- key: ${{ env "DECK_CONSUMER_KEY_JASON" }}
username: Jason
Please note that you must always prefix the environment variables name with "DECK_".
This allows you to keep sensitive information out of version control whilst still controlling your gateway configuration declaratively.
Please read the changelog for a complete list of changes.
You can get decK 1.7.0 on the GitHub releases page, where we offer downloads for Windows, macOS and Linux.
Built for developers We’ve taken the best parts of Terraform, deck, the AWS CLI, and more of your favorite tools and combined them into something that’s really special. kongctl takes inspiration from the AWS CLI, with support for profiles. Profiles
API gateways serve as the final checkpoint for your APIs. As such, gateway configuration is critical to ensuring that your APIs remain secure, available, and responsive. Ensuring that all changes to these configurations are intentional and follow yo
Managed Redis cache is a turnkey "Shared State" add-on for Kong Dedicated Cloud Gateways. It is designed to combine the performance of an in-memory data store with the simplicity of a SaaS product. When you spin up a Dedicated Cloud Gateway in Kong
With Kong Ingress Controller, when your Control Plane was hosted in Kong Konnect, and you were using Kubernetes Gateway API, your dataplane, routes, and services were in read-only mode. When using Kong Ingress Controller with Kubernetes Gateway API
Architecture Overview A multicloud DCGW architecture typically contains three main layers. 1\. Konnect Control Plane The SaaS control plane manages configuration, plugins, and policies. All gateways connect securely to this layer. 2\. Dedicated C
The Shifting Economic Landscape: The AI token economy in 2026 is evolving, and enterprise leaders must distinguish between low-cost input tokens and high-premium output tokens to maintain profitability. Agentic AI Financial Risks: The transition t
Imagine 47 million requests hitting your platform last month. Can you prove who made each one—and invoice with confidence? If that question tightens your stomach, you're not alone. Metered billing for APIs promises fair, transparent pricing that s