If you've not heard of decK (our declarative configuration and drift detection tool for [Kong Gateway](https://konghq.com/kong)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](https://github.com/Kong/deck)open source as usual.
v1.7.0 adds lots of [Konnect](https://konghq.com/kong-konnect)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](https://konghq.com/blog/apiops-devops-and-gitops-applied-to-api-lifecycle-end-to-end-automation-throughout-the-api-lifecycle)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](https://github.com/mmorel-35)@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](https://github.com/Kong/deck/blob/main/CHANGELOG.md#v170---20210520)changelog for a complete list of changes.
You can get decK 1.7.0 on the [GitHub releases page](https://github.com/Kong/deck/releases/tag/v1.7.0)GitHub releases page, where we offer downloads for Windows, macOS and Linux.
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
You invested in Kong Konnect. You centralized your API governance, locked down your routing, enforced your security policies, and gave your organization a single source of truth for every API in your estate. That work is done, and it is working. So
kongctl was built with the modern development stack in mind. Developers working in a terminal want the ability to query systems quickly to verify state, behaviors, and capabilities. Coding harnesses need well defined tools and accurate schemas for
Agent-to-agent communication is the next frontier of AI infrastructure. As teams decompose monolithic AI workflows into specialized agents — a research agent, a booking agent, a summarization agent — the calls between those agents become as importa
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
