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 Kubernetes. Kong Gateway Operator (KGO) 1.2 brings six new features plus a brand new Helm chart that allows you to deploy KGO using tools that you already know and love.

The latest release of decK's APIOps features with the Kong Ingress Controller advances API management and automation in Kubernetes environments. This blog post delves into how this integration streamlines operations, ensuring a more feature-rich API lifecycle management.

Distributed architectures have become an integral part of modern digital landscape. With the proliferation of cloud computing, big data, and highly available systems, traditional monolithic architectures have given way to more distributed, scalable, and resilient designs. In this blog, we look at what makes an application distributed and how distributed applications work to bring about high availability, scalability, and resilience.

In this blog post, we’ll demonstrate how easy it is to use Gateway API HTTPRoutes to route traffic to workloads deployed in different namespaces in a single Kubernetes cluster — a process that’s easier than ever. Previously, we only had Ingress API to define ingress routing rules. It served us well, but it also had its flaws and limitations that we had to overcome, sometimes in a hacky way.

Kong’s Wanny Morellato and Deepak Mohandas recently joined Justin and Autumn on the ShipIt podcast to talk hybrid infrastructure with Kong Gateway and Kong Mesh. They unravel the complexities of hybrid infrastructure at scale, discussing the processes, strategies, and philosophies that drive continuous delivery, infrastructure as code, and more.

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 maturity requires a clear understanding of the stages involved and a commitment to evolving practices and strategies that best suit the organization's unique needs and goals.

The Kong Konnect team recently launched the Portal Management API, which allows users to manage their Developer Portals with one API. That means you can easily manage your portal settings, appearance, application registrations, and registration settings easier than before. In this blog, I’ll walk you through two scenarios that we expect the portal management API can help streamline.

Today we’re excited to announce that Kong Insomnia has shipped Storage Control, a new enterprise capability that allows administrators in an Insomnia organization to mandate what type of backend storage developers are allowed to use when creating API assets like API collections, API specifications, environments configuration, authentications data, and more.

Looking to develop more APIs faster (and securely)? Then you have some different API platform deployment models to consider. In this post, we'll define and compare the siloed, centralized, and federated API platform deployment models — and dive into why federated API management is key to striking a balance between agility and governance.

In this post, we're going to explore Karpenter, the ultimate solution for Node Autoscaling. Karpenter provides a cost-effective capability to implement your Kong Konnect Data Plane layer using the best EC2 Instances Types options available for your Kubernetes Nodes. See the previous posts in this series for more on Data Plane Elasticity and Pod Autoscaling with VPA, HPA, and Node Autoscaling with Cluster Autoscaler on Amazon EKS 1.29.