A common requirement for APIs is to rewrite the published URL to a different URL for the upstream service’s endpoint. For example, due to legacy reasons, your upstream endpoint may have a base URI like /api/oilers/. However, you want your publicly accessible API endpoint to now be named /titans/api.
After a full year of development since our last major open source release, we are proud to announce the next chapter of our flagship open-source API gateway — Kong Gateway 2.0 is generally available! With this release, Kong will become more operationally agnostic for large-scale deployments across on-premises and multi-cloud environments, thanks to the new Hybrid Mode. In addition, plugin development also becomes more language agnostic, thanks to the new Golang PDK support.
Happy New Year! To kick off 2020, we’re proud to announce Kuma’s 0.3.2 release that includes long, anticipated features. The most prominent one is Kong Gateway support for ingress into your Kuma mesh. Another exciting feature that was widely requested is Prometheus support, which will enable you to scrape your applications’ metrics. Lastly, we announced the Kuma GUI in the last release. Thanks to a lot of early feedback, we’ve added many exciting improvements in this release.
As some of you already know, I have been following the shift towards microservices adoption for a while now. For the longest time, when the industry thought of the transition to microservices, they thought of smaller companies leading the charge. However, I’ve seen large enterprises get value from microservices as well and saw this trickle-in starting in 2016, which is why I am excited to learn this now has achieved mainstream adoption.
Kong for Kubernetes (Kong for K8S) is a Kubernetes Ingress Controller based on the popular Kong Gateway open source project. Kong for K8S is fully Kubernetes Native and provides enhanced API management capabilities. From an architectural perspective, Kong for K8S consists of two parts: A Kubernetes controller, which manages the state of Kong for K8S ingress configuration, and the Kong Gateway which processes and manages incoming API requests.
Welcome to another hands-on Kuma guide! In the first guide, I walked you through securing an application using Kuma in a Kubernetes deployment. Since Kuma is platform-agnostic, I wanted to write a follow-up blog post on how to secure your application if you are not running in Kubernetes. This capability to run anywhere differentiates Kuma from many other service mesh solutions in the market.
As I look back at 2019 and all the amazing things we’ve achieved as a team, it was a big year for us at Kong. We’ve grown tremendously in just the past year alone, doubling to more than 160 employees, reaching 170 Kong Enterprise customers, hitting 100 million downloads of our open source Kong Gateway and running more than 1 million instances of Kong per month across the world.
Welcome to our second hands-on Kuma guide! The first one walked you through securing your application with mTLS using Kuma. Today, this guide will walk you through Kuma’s new L4 traffic routing rules. These rules will allow you to easily implement blue/green deployments and canary releases. In summary, Kuma will now alleviate the stress of deploying new versions and/or features into your service mesh. Let’s take a glimpse at how to achieve it in our sample application.
At KubeCon North America 2019, the community provided us with a ton of feedback and feature requests. We’re proud to release some of the most widely requested features in our latest version of Kuma: third-party CA (Certificate Authority) support, health checks, and a GUI! Kuma’s new health checks will help minimize the number of failed requests between your application. The third-party CA support will provide more flexibility when deciding how to secure your mesh.
