The Kubernetes Gateway API represents a massive collaborative effort and key advancement in Kubernetes networking. Developed by multiple vendors and community members, the Gateway API provides a robust and extensible new standard for managing ingress traffic. With the recent general availability of version 1.0.0, the Gateway API is now ready for production use. The release of the Gateway API is a major milestone for Kubernetes networking that has the potential to simplify and enhance ingress management.

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 grown it's become clear that there exists a greater need than Ingress is able to deliver.

We are excited to announce the latest minor release of Kuma 2.5.0. We’re in the last stride of publishing this release, but I believe the features we’re landing are important enough to start teasing you about it. Let’s focus on three main features.

Kubernetes took the world by storm in 2014. A CLI-first experience, containers as a first-class citizen, and a need to dynamically scale workloads meant that Kubernetes was the right choice for many teams moving to the cloud. By late 2015, the community realized that there needed to be a standard way to manage traffic at the edge of a cluster and so the Ingress API was born.

Whether ordering groceries online, checking your bank balance, or tracking a delivery, APIs are behind the scenes making it all possible. They're the backbone of the digital experiences that drive our interconnected global economy. You may know that. But beyond the convenient (and sometimes delightful) experiences APIs enable, how are APIs actually affecting the global economy and shaping the future course of business and technology? We wanted to know, so we found out.

Discover how API management and service mesh can go hand in hand toward secured platforms Over the last ten years, Kongers have witnessed hundreds of companies adopting a full lifecycle API management platform and have been working with the people behind the scenes, the “API tribes.” We’ve also learned from the field that API tribes most often have to deal with heterogeneous platforms, infrastructures, and clouds.

Imagine this: You're documenting an unreleased feature, and your documentation requires screenshots. However, you're working in an internal environment that includes features you don't want to reveal to the public. What do you do? We faced this exact situation during the API Summit release when we needed to capture screenshots of the new Kong Konnect Plus dashboard while our internal environment also showcased Mesh Manager features.

Modern software design relies heavily on distributed systems architecture, requiring all APIs to be robust and secure. GraphQL is no exception and is commonly served over HTTP, subjecting it to the same management concerns as any REST-based API. In fact, GraphQL’s dynamic client querying capabilities may lead to more complex and potent attack surfaces than traditional REST-based APIs.

Everyone’s talking AI — or artificial intelligence. But much of that talk falls into one of two extremes: AI will fix everything or AI will ruin everything.

With Kong Insomnia 8.3 (available today) we’ve brought back 100% local storage with no cloud synchronization for your projects, while at the same time keeping the same workflow for users who want to collaborate in the cloud. To start using Local Vault, get started for free with Insomnia.