What's New in Kong Gateway 3.7?

We're thrilled to announce the general availability of Kong Gateway 3.7 and Kong Gateway Enterprise 3.7. Along with enhancements and new features for both OSS and enterprise users, this version comes with the general availability of our edge AI Gateway. This release offers a brand new context…
Introducing the World’s First OSS Production-Grade Gateway API Operator

Today’s the day you’ve all been waiting for: Kong Gateway Operator OSS is here. You can read the code and see what a production-grade Kubernetes operator looks like . Authored by multiple Gateway API contributors, Kong Gateway Operator is the de-facto reference for Gateway API implementers on…
API Platform Engineering Maturity Model

APIs have become fundamental to the digital economy, enabling integration and communication between different systems and services. A mature API platform is not just a technical achievement but a strategic asset that can drive innovation, efficiency, and growth. However, reaching this level of…
Announcing Kong’s New Open Source AI Gateway

Today I’m excited to announce that Kong has released six new open source AI plugins in Kong Gateway 3.6 that turn every Kong Gateway deployment into an AI Gateway . These new plugins are available today and are entirely free and open source for everyone. The six new plugins are AI Proxy, AI…
Kong Konnect Data Plane Elasticity on Amazon EKS 1.29: Pod Autoscaling with VPA

In this series of posts, we will look closely at how Kong Konnect Data Planes can take advantage of Autoscalers running on Amazon Elastic Kubernetes Services (EKS) 1.29 to support the throughput the demands API consumers impose on it at the lowest cost. The series comprises four parts: One of the…
Using ChatGPT to Reinvigorate APIs

In this post, we’ll see how ChatGPT can be used to reinvigorate APIs by creating an OpenAPI specification for an existing API that has existing documentation. ChatGPT , developed by OpenAI , has generated attention for its natural language processing capabilities. ChatGPT is based on machine…
Gateway API: From Early Years to GA

In the Kubernetes world, the Ingress API has been the longstanding staple for getting access to your Services from outside your cluster network. Ingress has served us well over the years and can be found present in several dozen different implementations, but as time has passed and Kubernetes has…
Kong SAML Plugin: Examples and Usage

This post is part of our Kong Champions series, where real Kong users walk you through technical challenges, use cases, and new technology they're using in their day-to-day. Sign up here to become a Kong Champion. As a Kong user, I've had the opportunity to dive deep into Kong's offerings. I've…
A UI Comes to OSS! Introducing Kong Manager Open Source

At Kong, we love APIs! They’re the foundation of modern architecture, and we believe they’re only going to expand in scope over time. We also support a number of different tools to manage APIs — from decK for declarative Kong Gateway configuration to Kong Insomnia for development and exploration of…
Build with Confidence: Beta API Specs Available Now

Few things are more frustrating than encountering a product with either no documentation or worse: documentation that leads you astray. When it comes to developing APIs, schemas typically define how requests and responses are formatted and guide how clients and services exchange data. Commonly,…
Kong Gateway 3.4 for OSS: Bring Your Own Language with WebAssembly!

The Kong Gateway 3.4 for Open Source (OSS) release is massive for our community users. Notably, this release introduces support for WebAssembly (Wasm), bringing a new level of extensibility and customization to Kong Gateway. Read on to learn more about the new capabilities in Kong Gateway 3.4 for…
How to Fix a SIGILL Kong Crash on Arm64

Kong will crash on the ARM64 platform (the machine with Mac M1/M2 chips or any ARM64 platform). The error message shows the crash is triggered by the SIGILL signal, which means there is an illegal instruction in the Kong binary code. And it turns out to be caused by an error in the LuaJIT…