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 your organization's best practices is key to maintaining a robust API gateway deployment. decK 1.28 adds a brand new feature that allows you to natively validate your gateway configurations against custom rule sets.

The latest release of Kong Mesh (version 2.5) brings many new features that push the envelope and make Kong Mesh the logical choice of a service mesh to meet your objectives. In this blog, we'll break down these new features and provide tailored use cases to illustrate how Kong Mesh 2.5 can elevate your service mesh experience. We'll focus on three main categories: flexibility, resiliency, and security.

In token-based architecture, tokens represent the client’s entitlement to access protected resources. Access tokens (or bearer tokens as they're commonly known) are issued by authorization servers after successful user authentication. The tokens are passed as credentials in the request to the target APIs which inform the API that the bearer of the token is authorized to access the API and perform certain actions.

Kong Gateway Enterprise 3.5 is packed with security features to support the use cases demanded by our enterprise customers through major improvements in Secrets Management integrations and our Open-ID Connect (OIDC) plugin. Additionally, we’ve added key security updates for a few of our AWS integrations.

We’re excited to announce the general availability of Kong Gateway 3.5 for Open Source (OSS). This release enables Javascript developers to extend the Gateway via the WebAssembly layer which is currently in Beta, delivers some enormous observability enhancements, and unlocks top-end performance. Keep reading for the latest on Kong Gateway 3.5 for OSS!

APIs have become a crucial part of modern software architecture, allowing different applications and services to communicate with each other. As organizations adopt microservices and distribute their systems, they require a cohesive API platform to manage these complex environments.

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.